Triple
T32576085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larne Lough |
E832647
|
entity |
| Predicate | shoreCharacter |
P13817
|
FINISHED |
| Object | mudflats and saltmarsh in upper lough |
—
|
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: mudflats and saltmarsh in upper lough | Statement: [Larne Lough, shoreCharacter, mudflats and saltmarsh in upper lough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoreCharacter Context triple: [Larne Lough, shoreCharacter, mudflats and saltmarsh in upper lough]
-
A.
shoreType
chosen
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
B.
shore
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
-
C.
shorelineCharacteristic
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
D.
shoreHas
Indicates that a shore possesses, contains, or is characterized by a particular feature, object, or attribute.
-
E.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63e3ac081908cd2ee069e971cea |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.