Triple
T763064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldsmobile Ninety-Eight |
E16112
|
entity |
| Predicate | positionInLineup |
P18925
|
FINISHED |
| Object | above Oldsmobile Eighty-Eight |
—
|
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: above Oldsmobile Eighty-Eight | Statement: [Oldsmobile Ninety-Eight, positionInLineup, above Oldsmobile Eighty-Eight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLineup Context triple: [Oldsmobile Ninety-Eight, positionInLineup, above Oldsmobile Eighty-Eight]
-
A.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
B.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
C.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
D.
positionOnRace
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
-
E.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6841f388190a6d08c3bf5c17fe4 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a506106081909ef97a679ff00a5a |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5a35c68819082429755c046e9a7 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.