Triple
T29288310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burns Waterway |
E742586
|
entity |
| Predicate | artificialChannel |
P166798
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Burns Waterway, artificialChannel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artificialChannel Context triple: [Burns Waterway, artificialChannel, true]
-
A.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
B.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
C.
linearChannel
Indicates a relationship where communication or flow occurs through a single, sequential path or medium, typically in one dimension or along a straight route.
-
D.
fictionalChannelNumber
Indicates that a channel is assigned a number that does not correspond to a real, physically existing broadcast or transmission channel.
-
E.
channelLining
Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6653dada88190b0c075cca6a40536 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1 p.m.