Triple
T14943443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Fleet (culverted) |
E372587
|
entity |
| Predicate | reasonForCulverting |
P116774
|
FINISHED |
| Object | public health concerns |
—
|
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: public health concerns | Statement: [River Fleet (culverted), reasonForCulverting, public health concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCulverting Context triple: [River Fleet (culverted), reasonForCulverting, public health concerns]
-
A.
causeOfDrainage
Indicates the factor or process that leads to or is responsible for the drainage of a substance, area, or system.
-
B.
majorDrainageFor
Indicates that one watercourse or drainage feature serves as the primary outlet or drainage system for another area or hydrologic feature.
-
C.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
D.
eraOfMajorDrainageWorks
Indicates the time period during which significant drainage or water-management construction activities took place.
-
E.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68c1df0819084c0cd61b207d398 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:38 a.m.