Triple
T21757437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuilcagh Mountain |
E537076
|
entity |
| Predicate | boardwalkBuiltTo |
P145242
|
FINISHED |
| Object | protect blanket bog |
—
|
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: protect blanket bog | Statement: [Cuilcagh Mountain, boardwalkBuiltTo, protect blanket bog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardwalkBuiltTo Context triple: [Cuilcagh Mountain, boardwalkBuiltTo, protect blanket bog]
-
A.
boardwalkType
Indicates the specific kind or classification of a boardwalk in relation to its general category or design.
-
B.
hasOutfieldBoardwalk
Indicates that an outfield area includes or is equipped with a boardwalk structure.
-
C.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
D.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
E.
walkThrough
Indicates moving through or along the interior or extent of something, typically traversing a space or environment from one side or point to another.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8f64d881909cf10fd420153b09 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4c438c819089ab285e64e81d24 |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:50 p.m.