Triple
T253687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fray Jorge National Park |
E5390
|
entity |
| Predicate | protectionObjective |
P8850
|
FINISHED |
| Object | conservation of unique coastal forest ecosystem |
—
|
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: conservation of unique coastal forest ecosystem | Statement: [Fray Jorge National Park, protectionObjective, conservation of unique coastal forest ecosystem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectionObjective Context triple: [Fray Jorge National Park, protectionObjective, conservation of unique coastal forest ecosystem]
-
A.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
B.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
E.
protectedIn
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d5331b48190b3797fece8e60e20 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b678d6c81909780e1995c1ca691 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.