Triple
T7531557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian Grand Prix |
E178033
|
entity |
| Predicate | constructorsTitleClinched |
P43074
|
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: [2014 Russian Grand Prix, constructorsTitleClinched, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorsTitleClinched Context triple: [2014 Russian Grand Prix, constructorsTitleClinched, true]
-
A.
clinchedBy
chosen
Indicates that a particular outcome, title, or achievement has been definitively secured or guaranteed by a specific entity.
-
B.
titleAcquiredBy
Indicates that a particular title, rank, or designation has been obtained or earned by a specific entity.
-
C.
hasConstructorTitle
Indicates that an entity is associated with a specific title or designation held in its role as a constructor.
-
D.
mastersTitles
Indicates that one entity holds one or more master's degree titles associated with another entity (such as an institution, field, or program).
-
E.
titleHoldersCollectively
Indicates that a group of entities jointly hold, share, or possess a particular title or set of titles as a collective.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8217b1c8190b3db453cee0fc4fd |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.