Triple
T18797389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1954 Argentine Grand Prix |
E459671
|
entity |
| Predicate | gridFromQualifying |
P133056
|
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: [1954 Argentine Grand Prix, gridFromQualifying, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridFromQualifying Context triple: [1954 Argentine Grand Prix, gridFromQualifying, true]
-
A.
pointsFromQualifying
Indicates that points are derived from or awarded based on a qualifying event, stage, or performance.
-
B.
qualifyingZones
Indicates that certain areas or regions meet specified criteria or conditions required for a particular status, activity, or classification.
-
C.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
D.
governsQualificationFrom
Indicates that an entity’s authority, status, or eligibility is derived from or determined by a specified qualification.
-
E.
qualifiesFrom
Indicates that one entity gains an official status, capability, or eligibility as a result of successfully completing or meeting the requirements of another entity.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a020821881909749f6a1c6cd195b |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.