Triple
T24801596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Rebels |
E620537
|
entity |
| Predicate | finishedPosition1915 |
P55492
|
FINISHED |
| Object | 3rd place |
—
|
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: 3rd place | Statement: [Pittsburgh Rebels, finishedPosition1915, 3rd place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishedPosition1915 Context triple: [Pittsburgh Rebels, finishedPosition1915, 3rd place]
-
A.
finishPosition
chosen
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
B.
finishedAheadOf
Indicates that one entity completed an event, task, or process before another entity, ranking or finishing in a superior or earlier position.
-
C.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
D.
finishMove
Indicates that an entity completes or brings to an end a movement or relocation action involving another entity or itself.
-
E.
finishedRecord
Indicates that an entity has completed or finalized the creation, processing, or updating of a record.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:49 a.m.