Triple
T6062649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witham Navigable Drains |
E135070
|
entity |
| Predicate | navigationLinkedTo |
P68422
|
FINISHED |
| Object | River Witham navigation |
—
|
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: River Witham navigation | Statement: [Witham Navigable Drains, navigationLinkedTo, River Witham navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationLinkedTo Context triple: [Witham Navigable Drains, navigationLinkedTo, River Witham navigation]
-
A.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
B.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
C.
linkedSite
Indicates that one site has an explicit hyperlink or reference connection to another site.
-
D.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
E.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
- F. None of above. chosen
Provenance (4 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0572100e8819084c3174921a2d527 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.