Triple
T21755542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orting, Washington |
E537028
|
entity |
| Predicate | hasHistoricRootIn |
P34787
|
FINISHED |
| Object | railroad industry |
—
|
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: railroad industry | Statement: [Orting, Washington, hasHistoricRootIn, railroad industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricRootIn Context triple: [Orting, Washington, hasHistoricRootIn, railroad industry]
-
A.
hasHistoricBasisIn
Indicates that something is grounded in, derived from, or justified by historical events, practices, or precedents.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoricalPrecursor
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
D.
hasAncestralRoots
chosen
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
E.
hasHistoricTerminal
Indicates that an entity possesses or is associated with a historically significant terminal facility or endpoint.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8d6d0081908e0ccfbccea58895 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.