Triple
T6850831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formula 2 Championship |
E158009
|
entity |
| Predicate | usesSpecEngine |
P72609
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Formula 2 Championship, usesSpecEngine, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpecEngine Context triple: [Formula 2 Championship, usesSpecEngine, true]
-
A.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
D.
includesDisplayEngine
Indicates that one entity contains or incorporates another entity that functions as a display engine.
-
E.
supportsSpecificationVersion
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
- F. None of above. chosen
Provenance (4 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84c45708190918adfc028252400 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:20 p.m.