Triple
T27142897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAL |
E681861
|
entity |
| Predicate | hasOperatorContext |
P171762
|
FINISHED |
| Object | Iarnród Éireann |
—
|
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: Iarnród Éireann | Statement: [BAL, hasOperatorContext, Iarnród Éireann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatorContext Context triple: [BAL, hasOperatorContext, Iarnród Éireann]
-
A.
hasOperatorSection
Indicates that something includes or is associated with a specific section intended for operators or operational use.
-
B.
isOperatorOn
Indicates that one entity serves as an operator responsible for operating, controlling, or managing another entity (such as a system, machine, or process).
-
C.
hasOwnerOperator
Indicates that an entity is owned and operated by a specified party, combining both ownership and operational responsibility in a single relationship.
-
D.
hasOperatorContractAuthority
Indicates that an entity has the legal or formal authority to enter into and manage operator contracts on behalf of another party or organization.
-
E.
hasOperatorContractStart
Indicates the date on which an operator’s contractual agreement with another entity begins.
- F. None of above. chosen
Provenance (4 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 27, 2026, 9:10 a.m.