Triple
T26348271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP 4250 |
E662830
|
entity |
| Predicate | hasCabLocation |
P36092
|
FINISHED |
| Object | front of locomotive |
—
|
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: front of locomotive | Statement: [SP 4250, hasCabLocation, front of locomotive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabLocation Context triple: [SP 4250, hasCabLocation, front of locomotive]
-
A.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
B.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
-
C.
cabLocation
chosen
Indicates the current geographic position of a cab in space (e.g., on a map or within a defined area).
-
D.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
E.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 26, 2026, 10:43 p.m.