Triple
T13769966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Área de Protección de Flora y Fauna |
E330853
|
entity |
| Predicate | tipoDeManejo |
P110881
|
FINISHED |
| Object | manejo con zonificación interna |
—
|
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: manejo con zonificación interna | Statement: [Área de Protección de Flora y Fauna, tipoDeManejo, manejo con zonificación interna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeManejo Context triple: [Área de Protección de Flora y Fauna, tipoDeManejo, manejo con zonificación interna]
-
A.
steeringType
Indicates the kind or mechanism of steering control used to direct the movement of an entity.
-
B.
typeOfHaulage
Indicates the kind or category of haulage service or transport operation associated with an entity.
-
C.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
D.
typeOfProcedureHandled
Indicates the specific kind or category of procedure that an entity is responsible for managing or processing.
-
E.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0233ecc48190b934f085d2501eb1 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:10 p.m.