Triple
T36226837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Initao |
E891122
|
entity |
| Predicate | hasProtectedEcosystem |
P203005
|
FINISHED |
| Object | limestone forest |
—
|
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: limestone forest | Statement: [Initao, hasProtectedEcosystem, limestone forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedEcosystem Context triple: [Initao, hasProtectedEcosystem, limestone forest]
-
A.
hasProtectedHabitat
chosen
Indicates that an entity has a designated area or environment set aside and managed specifically for its protection or conservation.
-
B.
protectsEcosystemType
Indicates that one entity safeguards, preserves, or maintains the health and integrity of a particular type of ecosystem.
-
C.
hasProtectedSpecies
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
-
D.
ecosystemsProtected
Indicates that certain ecosystems are safeguarded from harm or degradation through conservation or protective measures.
-
E.
hasProtectedWatershed
Indicates that an entity possesses or is associated with a watershed area that is legally or formally protected for conservation or resource management purposes.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.