Triple
T28864795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strid |
E728968
|
entity |
| Predicate | riverCrossSection |
P117097
|
FINISHED |
| Object | very narrow |
—
|
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: very narrow | Statement: [The Strid, riverCrossSection, very narrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossSection Context triple: [The Strid, riverCrossSection, very narrow]
-
A.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
B.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
-
C.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
D.
watercourseProgression
Indicates the downstream sequence in which a watercourse flows into other water bodies or watercourses.
-
E.
waterwayWidth
chosen
Indicates the measured width of a waterway, typically the distance across it from one bank or edge to the opposite.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:48 a.m.