Triple
T6357432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itonama people |
E143025
|
entity |
| Predicate | associatedWithEcosystem |
P54308
|
FINISHED |
| Object | flooded savannas |
—
|
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: flooded savannas | Statement: [Itonama people, associatedWithEcosystem, flooded savannas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEcosystem Context triple: [Itonama people, associatedWithEcosystem, flooded savannas]
-
A.
sharesEcosystemWith
Indicates that two entities inhabit and interact within the same ecological system or environment.
-
B.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
C.
operatesInEcosystem
chosen
Indicates that an entity functions, behaves, or carries out its activities within a particular ecosystem or environmental context.
-
D.
containsEcosystem
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
E.
supportsEcosystemType
Indicates that one entity provides suitable conditions or resources necessary to sustain or maintain a particular type of ecosystem.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f5bdd481909cf9db595ddb27df |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.