Triple
T22154408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartmouth Steam Railway |
E547495
|
entity |
| Predicate | infrastructureOwnerType |
P109389
|
FINISHED |
| Object | private company |
—
|
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: private company | Statement: [Dartmouth Steam Railway, infrastructureOwnerType, private company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureOwnerType Context triple: [Dartmouth Steam Railway, infrastructureOwnerType, private company]
-
A.
hasInfrastructureOwnerType
chosen
Indicates the type or category of entity that owns or is responsible for a given piece of infrastructure.
-
B.
ownerOfInfrastructureUsed
Indicates that one entity owns the infrastructure that is being used by another entity or activity.
-
C.
hasInfrastructureOwner
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
D.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
E.
infrastructureLeasedTo
Indicates that infrastructure owned or controlled by one party is leased or rented out for use by another party under a contractual agreement.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f6d5b88190badee2e515a3b633 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.