Triple
T4449580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huddersfield Narrow Canal |
E96374
|
entity |
| Predicate | originallyOpened |
P22100
|
FINISHED |
| Object | 1811 |
—
|
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: 1811 | Statement: [Huddersfield Narrow Canal, originallyOpened, 1811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyOpened Context triple: [Huddersfield Narrow Canal, originallyOpened, 1811]
-
A.
originallyOpenedBy
Indicates that an entity was first opened, launched, or made operational by a specific agent or organization.
-
B.
firstOpenedAt
chosen
Indicates the date and time at which something was initially opened for the first time.
-
C.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d5975c8190bfe8a2d5d2dbf075 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.