Triple
T37583969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware and Hudson Canal Company |
E935046
|
entity |
| Predicate | canalName |
P188736
|
FINISHED |
| Object | Delaware and Hudson Canal |
—
|
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: Delaware and Hudson Canal | Statement: [Delaware and Hudson Canal Company, canalName, Delaware and Hudson Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canalName Context triple: [Delaware and Hudson Canal Company, canalName, Delaware and Hudson Canal]
-
A.
containsCanal
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
B.
usedCanal
Indicates that an entity made use of a canal as a route, resource, or means to perform an action or achieve a purpose.
-
C.
canalProject
Indicates that an entity is involved in, associated with, or designated as a canal construction or development project.
-
D.
canalOpened
Indicates that a canal has been officially opened or put into operation.
-
E.
canalStatus
Indicates the operational or physical condition of a canal, such as whether it is open, closed, restricted, or otherwise affected.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.