Triple
T37250564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarée |
E923974
|
entity |
| Predicate | valleyProtectionStatus |
P3029
|
FINISHED |
| Object | protected area |
—
|
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: protected area | Statement: [Clarée, valleyProtectionStatus, protected area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valleyProtectionStatus Context triple: [Clarée, valleyProtectionStatus, protected area]
-
A.
valleyLandscapeStatus
Indicates the condition or classification of a valley’s landscape at a given time.
-
B.
isProtectedAreaStatus
Indicates that an entity has a designated protection status, typically signifying legal or formal recognition as a protected area.
-
C.
hasProtectedAreaStatus
chosen
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
D.
valueProtected
Indicates that a value is safeguarded from unauthorized access, modification, or exposure.
-
E.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.