Triple
T35583361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelkie Junction, Michigan |
E1028279
|
entity |
| Predicate | railTransportStatus |
P41715
|
FINISHED |
| Object | former junction |
—
|
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: former junction | Statement: [Pelkie Junction, Michigan, railTransportStatus, former junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railTransportStatus Context triple: [Pelkie Junction, Michigan, railTransportStatus, former junction]
-
A.
railStatus
chosen
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
B.
followingTrainStatus
Indicates that one entity is tracking or monitoring the current operational status or progress of a train.
-
C.
statusOfTrain7
Indicates the current operational status or condition of train number 7 in relation to its schedule or service.
-
D.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
-
E.
railLineStatusAfterward
Indicates the condition or operational status of a rail line after a specified event or time period has occurred.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.