Triple
T30050437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Street, Belfast |
E763586
|
entity |
| Predicate | underlyingWatercourseStatus |
P181241
|
FINISHED |
| Object | culverted |
—
|
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: culverted | Statement: [High Street, Belfast, underlyingWatercourseStatus, culverted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingWatercourseStatus Context triple: [High Street, Belfast, underlyingWatercourseStatus, culverted]
-
A.
waterwayStatus
Indicates the current navigational or operational condition of a waterway, such as whether it is open, restricted, or closed for use.
-
B.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
-
C.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
riverStatusAtLocation
Indicates the condition or state of a river at a specific geographic location.
-
E.
isOnWatercourse
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 29, 2026, 6:55 p.m.