Triple
T27488945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Pacific AC-6 |
E693824
|
entity |
| Predicate | classPredecessor |
P10130
|
FINISHED |
| Object | Southern Pacific AC-5 |
—
|
NE NERFINISHED |
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: Southern Pacific AC-5 | Statement: [Southern Pacific AC-6, classPredecessor, Southern Pacific AC-5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classPredecessor Context triple: [Southern Pacific AC-6, classPredecessor, Southern Pacific AC-5]
-
A.
predecessorClass
chosen
Indicates that one class precedes another in an ordered sequence or hierarchy, typically representing an earlier version or prior stage of that class.
-
B.
calledPredecessorOf
Indicates that one entity is referred to or designated as the predecessor of another entity.
-
C.
predecessorCollectionOf
Indicates that one collection temporally or sequentially comes before and leads into another collection.
-
D.
predecessorFunction
Indicates a function that maps each element to its immediate predecessor in an ordered sequence or structure.
-
E.
classPrecededBy
Indicates that one class occurs or is scheduled before another class in a sequence or timetable.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 1:04 p.m.