Triple
T6367927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meelick Lock |
E143272
|
entity |
| Predicate | connectsSectionOf |
P845
|
FINISHED |
| Object | upper River Shannon |
—
|
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 River Shannon | Statement: [Meelick Lock, connectsSectionOf, upper River Shannon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsSectionOf Context triple: [Meelick Lock, connectsSectionOf, upper River Shannon]
-
A.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
B.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
C.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
D.
connectsArea
Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
-
E.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of another entity.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068251ae48190af8201d5f9ad35b6 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.