Triple
T34944575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lago de San Mauricio |
E1007820
|
entity |
| Predicate | tipoDeÁreaProtegida |
P110335
|
FINISHED |
| Object | parque nacional |
—
|
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: parque nacional | Statement: [Lago de San Mauricio, tipoDeÁreaProtegida, parque nacional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeÁreaProtegida Context triple: [Lago de San Mauricio, tipoDeÁreaProtegida, parque nacional]
-
A.
typeOfProtectedAreasSystem
Indicates that one protected area belongs to, or is classified under, a particular system or framework of protected areas.
-
B.
stateProtectedAreaType
Indicates that an area is designated as a specific type or category of state-protected area.
-
C.
relatedProtectedAreaType
Indicates that one protected area is associated with another through a specific type of protected-area relationship or classification.
-
D.
typeOfProtectedAreasManaged
Indicates the specific categories or kinds of protected areas that an entity is responsible for managing.
-
E.
isTypeOfProtectedArea
chosen
Indicates that one entity is classified as a specific type or category of protected area in relation to another entity.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.