Triple
T6603861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lough Allen |
E149062
|
entity |
| Predicate | positionInRiverSystem |
P71990
|
FINISHED |
| Object | upper Shannon lake |
—
|
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: upper Shannon lake | Statement: [Lough Allen, positionInRiverSystem, upper Shannon lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRiverSystem Context triple: [Lough Allen, positionInRiverSystem, upper Shannon lake]
-
A.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
-
B.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
C.
situatedUpstreamOf
Indicates that one entity is located in the direction from which a flow (such as water, traffic, or a process stream) originates relative to another entity along the same path or system.
-
D.
locatedBetweenRivers
Indicates that something is situated in the area or region bounded or flanked by two rivers.
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:56 p.m.