Triple
T26678675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parnell Bridge, Cork |
E672541
|
entity |
| Predicate | isInWatercourseSystem |
P63896
|
FINISHED |
| Object | River Lee system |
—
|
NE NERFINISHED |
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 Lee system | Statement: [Parnell Bridge, Cork, isInWatercourseSystem, River Lee system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInWatercourseSystem Context triple: [Parnell Bridge, Cork, isInWatercourseSystem, River Lee system]
-
A.
isInWaterwaySystem
chosen
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
-
B.
isOnWatercourse
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
C.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
-
D.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
E.
isNaturalWatercourse
Indicates that one entity is a naturally formed flowing body of water (such as a river or stream), rather than an artificial or man-made channel.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617060fc8819095d063081288880d |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:18 a.m.