Triple
T30067835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Branch Valley Railroad |
E764083
|
entity |
| Predicate | trackClass |
P3832
|
FINISHED |
| Object | freight branch |
—
|
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: freight branch | Statement: [South Branch Valley Railroad, trackClass, freight branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackClass Context triple: [South Branch Valley Railroad, trackClass, freight branch]
-
A.
trackFeature
Indicates that one entity monitors, records, or follows the behavior, state, or evolution of a particular feature associated with another entity.
-
B.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
C.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
trackSegment
Indicates a specific portion or section of a larger track or route that is treated as a distinct segment.
-
E.
trackSystem
Indicates a relationship where one entity monitors, records, or follows the status, behavior, or changes of another entity within a system.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 7 p.m.