Triple
T26348272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP 4250 |
E662830
|
entity |
| Predicate | smokeboxLocation |
P160437
|
FINISHED |
| Object | rear 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: rear of locomotive | Statement: [SP 4250, smokeboxLocation, rear of locomotive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smokeboxLocation Context triple: [SP 4250, smokeboxLocation, rear of locomotive]
-
A.
smokingLocation
Indicates the place or environment where the act of smoking occurs or is permitted.
-
B.
smokeSystem
Indicates that an entity is equipped with or associated with a smoke-generating system (e.g., for signaling, testing, or special effects).
-
C.
slotLocation
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
-
D.
smokeLevel
Indicates the intensity or concentration of smoke present in or produced by an entity or environment.
-
E.
hasSmokehouse
Indicates that one entity possesses, contains, or includes a smokehouse as part of its facilities or properties.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa904a08190938352e5413c1e77 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:43 p.m.