Triple
T34157914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockland, Ohio |
E876191
|
entity |
| Predicate | historicallyLocatedAlong |
P2409
|
FINISHED |
| Object | Miami and Erie 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: Miami and Erie Canal | Statement: [Lockland, Ohio, historicallyLocatedAlong, Miami and Erie Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyLocatedAlong Context triple: [Lockland, Ohio, historicallyLocatedAlong, Miami and Erie Canal]
-
A.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
B.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
C.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
historicallyPlacedIn
Indicates that an entity was located or situated in a particular place during a specific historical period or context.
-
E.
historicallyLocatedOutside
Indicates that an entity was historically situated beyond the boundaries or limits of another specified place or region.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 1, 2026, 1:54 a.m.