Triple
T2237247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calakmul |
E49310
|
entity |
| Predicate | locatedInEcosystem |
P40
|
FINISHED |
| Object | tropical rainforest |
—
|
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: tropical rainforest | Statement: [Calakmul, locatedInEcosystem, tropical rainforest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInEcosystem Context triple: [Calakmul, locatedInEcosystem, tropical rainforest]
-
A.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
B.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
C.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
E.
isEcologicalZone
Indicates that one entity functions as, or is classified as, an ecological zone 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09573848190bf91eddcc2fa0061 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.