Triple
T34530304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mountain Rocket |
E886516
|
entity |
| Predicate | branchService |
P12340
|
FINISHED |
| Object | Limon–Denver segment |
—
|
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: Limon–Denver segment | Statement: [Rocky Mountain Rocket, branchService, Limon–Denver segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchService Context triple: [Rocky Mountain Rocket, branchService, Limon–Denver segment]
-
A.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
serviceBranchChange
Indicates a change in an entity’s affiliated service branch from one branch to another.
-
C.
branchNetwork
chosen
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
-
D.
serviceBranchSpecific
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
E.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fbecabc8190956d708dbf2d2c48 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.