Triple
T1768824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banbury |
E38824
|
entity |
| Predicate | hasCanalFacility |
P12416
|
FINISHED |
| Object | narrowboat moorings |
—
|
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: narrowboat moorings | Statement: [Banbury, hasCanalFacility, narrowboat moorings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanalFacility Context triple: [Banbury, hasCanalFacility, narrowboat moorings]
-
A.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
-
B.
hasCanalSection
Indicates a relationship where one entity includes, contains, or is associated with a specific section or segment of a canal.
-
C.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
D.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
hasBranchCanals
Indicates that an entity possesses or is connected to one or more subsidiary or secondary canals branching off from a main canal.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.