Triple
T37583985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware and Hudson Canal Company |
E935046
|
entity |
| Predicate | transportedToMarket |
P122262
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [Delaware and Hudson Canal Company, transportedToMarket, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedToMarket Context triple: [Delaware and Hudson Canal Company, transportedToMarket, New York City]
-
A.
transportedAfter
Indicates that one entity is transported only after the transportation of another entity has occurred in time.
-
B.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
-
C.
transportedIn
Indicates that one entity is carried or conveyed inside another entity as a means of transport.
-
D.
transportedAs
Indicates that one entity is moved or carried from one place to another in the form, role, or medium specified by another entity.
-
E.
transportedBetween
chosen
Indicates that an entity is moved or conveyed from one specified location or state to another.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:17 p.m.