Triple
T34026066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doomben line services |
E872508
|
entity |
| Predicate | ownershipOfInfrastructure |
P26836
|
FINISHED |
| Object | Queensland Rail |
—
|
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: Queensland Rail | Statement: [Doomben line services, ownershipOfInfrastructure, Queensland Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipOfInfrastructure Context triple: [Doomben line services, ownershipOfInfrastructure, Queensland Rail]
-
A.
ownerOfInfrastructureUsed
Indicates that one entity owns the infrastructure that is being used by another entity or activity.
-
B.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
C.
hasInfrastructureOwner
chosen
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
D.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
E.
hasInfrastructureOwnerType
Indicates the type or category of entity that owns or is responsible for a given piece of infrastructure.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:51 a.m.