Triple
T31433697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ET&WNC Railroad corridor |
E801865
|
entity |
| Predicate | eraOfPrimaryOperation |
P97447
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [ET&WNC Railroad corridor, eraOfPrimaryOperation, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfPrimaryOperation Context triple: [ET&WNC Railroad corridor, eraOfPrimaryOperation, late 19th century]
-
A.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
B.
eraOfMajorOperation
chosen
Indicates the historical period during which a major operation primarily took place or was most active.
-
C.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
D.
eraOfPrimaryEquipment
Indicates the historical time period during which the primary equipment associated with an entity was originally designed, produced, or predominantly used.
-
E.
eraOfPrimaryAttestation
Indicates the historical time period during which the primary evidence or attestation of something first appears.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 30, 2026, 8:59 p.m.