Triple
T18098633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEICO 500 |
E433154
|
entity |
| Predicate | typeOfFinishOften |
P84337
|
FINISHED |
| Object | photo finish |
—
|
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: photo finish | Statement: [GEICO 500, typeOfFinishOften, photo finish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFinishOften Context triple: [GEICO 500, typeOfFinishOften, photo finish]
-
A.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
B.
hasTypicalFinish
chosen
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
C.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
D.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied to another entity.
-
E.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb3ef548190a322f98917b54a59 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.