Triple
T37583987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware and Hudson Canal Company |
E935046
|
entity |
| Predicate | transportedFromRegion |
P410
|
FINISHED |
| Object | Lackawanna Valley, Pennsylvania |
—
|
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: Lackawanna Valley, Pennsylvania | Statement: [Delaware and Hudson Canal Company, transportedFromRegion, Lackawanna Valley, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedFromRegion Context triple: [Delaware and Hudson Canal Company, transportedFromRegion, Lackawanna Valley, Pennsylvania]
-
A.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
-
B.
transferredRegion
Indicates that control, ownership, or responsibility for a geographic or administrative region has been moved from one entity to another.
-
C.
regionOfMigration
Indicates the geographic area from which an entity or population moves or migrates.
-
D.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
E.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
- 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_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.