Triple
T7195921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaxchilán |
E168613
|
entity |
| Predicate | isInEnvironment |
P13810
|
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: [Yaxchilán, isInEnvironment, tropical rainforest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInEnvironment Context triple: [Yaxchilán, isInEnvironment, tropical rainforest]
-
A.
isEnvironmentOf
Indicates that one entity serves as the surrounding conditions, context, or setting in which another entity exists, operates, or occurs.
-
B.
usedInEnvironment
Indicates that something is utilized or operates within a particular environment or context.
-
C.
isInSystem
Indicates that one entity is located within, belongs to, or is contained by a particular system.
-
D.
hasEnvironmentType
chosen
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
E.
hasEnvironmentalFunction
Indicates that an entity serves a specific role or purpose related to the environment, such as contributing to ecological processes, protection, or sustainability.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e927709c81909edf6ee42fe7f833 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:51 p.m.