Triple
T33045270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1969 United States Grand Prix |
E845576
|
entity |
| Predicate | seasonRaceNumber |
P120082
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [1969 United States Grand Prix, seasonRaceNumber, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRaceNumber Context triple: [1969 United States Grand Prix, seasonRaceNumber, 11]
-
A.
raceNumberInSeason
chosen
Indicates the ordinal position of a specific race within the sequence of races in a given season.
-
B.
raceNumberInSeries
Indicates the ordinal position of a specific race within a larger race series or sequence.
-
C.
racingNumber
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
-
D.
raceNumberAtTrack
Indicates the specific ordinal number assigned to a race within the sequence of races held at a particular track.
-
E.
notableRaceNumber
Indicates that a specific race is distinguished as notable for an entity, typically by assigning it a particular identifying number.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:24 a.m.