Triple
T11439461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Chimney |
E271102
|
entity |
| Predicate | routeStatus |
P99307
|
FINISHED |
| Object | commonly used on classic Abruzzi Spur line |
—
|
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: commonly used on classic Abruzzi Spur line | Statement: [House Chimney, routeStatus, commonly used on classic Abruzzi Spur line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeStatus Context triple: [House Chimney, routeStatus, commonly used on classic Abruzzi Spur line]
-
A.
routeRequirementStatus
Indicates the current status or condition of a specified route’s required criteria being met or unmet.
-
B.
routeAvailability
Indicates whether a particular route between two points is currently available for use.
-
C.
routeCompleted
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
D.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
E.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d800115af08190bba53dd3ff561ca1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:35 p.m.