Triple
T7896012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mono runtime |
E183343
|
entity |
| Predicate | supportsRuntimeMode |
P203
|
FINISHED |
| Object | JIT compilation |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: JIT compilation | Statement: [Mono runtime, supportsRuntimeMode, JIT compilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRuntimeMode Context triple: [Mono runtime, supportsRuntimeMode, JIT compilation]
-
A.
supportsModule
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
hasPrimaryRuntime
Indicates that an entity is associated with a main or default runtime environment it primarily uses or depends on.
-
D.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
E.
supportsReferenceModes
Indicates that an entity provides or is compatible with specific reference modes for identifying or accessing other entities.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a174574819084270dbb6fcbb7fe |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.