Triple
T6306256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehigh and Hudson River Railway |
E141381
|
entity |
| Predicate | operatedAsIndependentUntil |
P43452
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Lehigh and Hudson River Railway, operatedAsIndependentUntil, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsIndependentUntil Context triple: [Lehigh and Hudson River Railway, operatedAsIndependentUntil, 1976]
-
A.
becameIndependentCompanyOn
Indicates the date on which an entity separated from a parent or larger organization and started operating as an independent company.
-
B.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
C.
wasIndependentUntil
chosen
Indicates that an entity possessed independent status or autonomy up to a specific point in time, after which that independence ceased.
-
D.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
E.
formerlyOperatedBy
Indicates that an entity was previously operated or managed by another entity, but is no longer under that operation.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06479acec819090306a155a03b774 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.