Triple
T37981971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Rail (historical) |
E947574
|
entity |
| Predicate | publicOwnershipStatus |
P7585
|
FINISHED |
| Object | publicly owned until lease of operations |
—
|
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: publicly owned until lease of operations | Statement: [BC Rail (historical), publicOwnershipStatus, publicly owned until lease of operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOwnershipStatus Context triple: [BC Rail (historical), publicOwnershipStatus, publicly owned until lease of operations]
-
A.
statusOwnership
Indicates that one entity holds ownership or control over the status or state associated with another entity.
-
B.
privateOwnership
Indicates that a specified entity holds legal ownership or control over something in a private, non-public capacity.
-
C.
ownershipType
chosen
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
D.
privateOwnershipShare
Indicates the proportion or share of ownership in an entity that is held by private (non-governmental) owners.
-
E.
ownershipSince
Indicates the point in time from which an entity has continuously owned another entity.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:20 p.m.