Triple
T6992485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Protection Area |
E162116
|
entity |
| Predicate | oftenOverlapsWith |
P1867
|
FINISHED |
| Object | Special Area of Conservation |
—
|
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: Special Area of Conservation | Statement: [Special Protection Area, oftenOverlapsWith, Special Area of Conservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenOverlapsWith Context triple: [Special Protection Area, oftenOverlapsWith, Special Area of Conservation]
-
A.
overlapsWith
chosen
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
B.
hasJurisdictionOverlapWith
Indicates that two authorities or entities share some portion of legal or regulatory control over the same area, subject, or set of activities.
-
C.
coincidesWith
Indicates that two entities occupy the same position, time, or state such that they exactly overlap or occur together.
-
D.
overlies
Indicates that one entity is positioned directly above and covering or resting on another entity, often with partial or complete contact.
-
E.
hasCommunityOverlap
Indicates that two entities share a portion of the same community, membership base, or audience.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc30fdc81909244d83c8178755c |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.