Triple
T16644955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajusco |
E404443
|
entity |
| Predicate | protectiveStatus |
P56582
|
FINISHED |
| Object | part of Ajusco National Park |
—
|
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: part of Ajusco National Park | Statement: [Ajusco, protectiveStatus, part of Ajusco National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectiveStatus Context triple: [Ajusco, protectiveStatus, part of Ajusco National Park]
-
A.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
B.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
protectionCategory
chosen
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
-
D.
stateProtected
Indicates that an entity is safeguarded or regulated under the laws, authority, or jurisdiction of a specific state.
-
E.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad4735c81908a3a227bf02ca489 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296af2f88819092c9ffee4a65d7dd |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.