Triple
T1088509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Managua |
E24106
|
entity |
| Predicate | shorelineFeature |
P6779
|
FINISHED |
| Object | urban shoreline at Managua |
—
|
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: urban shoreline at Managua | Statement: [Lake Managua, shorelineFeature, urban shoreline at Managua]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineFeature Context triple: [Lake Managua, shorelineFeature, urban shoreline at Managua]
-
A.
coastlineFeature
chosen
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
B.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
C.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
D.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
E.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97d85708190a1630256648aa4a2 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b741b0cc8190be001a16a81f6d9e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.