Triple
T2462844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reserva de Producción de Fauna Chimborazo |
E54571
|
entity |
| Predicate | allowsUse |
P7913
|
FINISHED |
| Object | regulated grazing of camelids |
—
|
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: regulated grazing of camelids | Statement: [Reserva de Producción de Fauna Chimborazo, allowsUse, regulated grazing of camelids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsUse Context triple: [Reserva de Producción de Fauna Chimborazo, allowsUse, regulated grazing of camelids]
-
A.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
eligibleUses
chosen
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
C.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.