Triple
T35770187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merredin |
E1034137
|
entity |
| Predicate | isOnWaterPipeline |
P36984
|
FINISHED |
| Object | Golden Pipeline |
—
|
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: Golden Pipeline | Statement: [Merredin, isOnWaterPipeline, Golden Pipeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnWaterPipeline Context triple: [Merredin, isOnWaterPipeline, Golden Pipeline]
-
A.
isOnWatercourse
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
B.
isPartOfWaterSystem
chosen
Indicates that one entity is a component, segment, or subsystem within a larger water distribution, treatment, or management system.
-
C.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
-
D.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
E.
isInlandWaterwayInfrastructure
Indicates that something is part of the physical facilities or structures used for inland waterway transport, such as canals, locks, or related navigational 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1f712ec8190a80c885dc84c44ab |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.