Triple
T38453321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glennock |
E912234
|
entity |
| Predicate | railwayOwnerInUniverse |
P96078
|
FINISHED |
| Object | Skarloey Railway Company |
—
|
NE NERFINISHED |
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: Skarloey Railway Company | Statement: [Glennock, railwayOwnerInUniverse, Skarloey Railway Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayOwnerInUniverse Context triple: [Glennock, railwayOwnerInUniverse, Skarloey Railway Company]
-
A.
railwayOwner
chosen
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
B.
railwayCarriageOwner
Indicates that one entity is the owner or legal possessor of a particular railway carriage.
-
C.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
D.
servesRollingStockOwner
Indicates that one entity provides services or functions in support of the owner of a piece of rolling stock (e.g., rail vehicles).
-
E.
laterRailwayCompany
Indicates that one railway company is the successor or later incarnation of another railway company.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:31 p.m.