Triple
T24732555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapidian language |
E618324
|
entity |
| Predicate | geographicEcology |
P157055
|
FINISHED |
| Object | Amazonian lowlands |
—
|
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: Amazonian lowlands | Statement: [Mapidian language, geographicEcology, Amazonian lowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicEcology Context triple: [Mapidian language, geographicEcology, Amazonian lowlands]
-
A.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
-
B.
geographicIsolation
Indicates that an entity is separated from others by physical distance or natural barriers, limiting interaction or exchange between them.
-
C.
geographicRangeType
Indicates the kind of geographic range or distribution pattern that characterizes where an entity occurs or is found.
-
D.
biogeographicRole
Indicates the ecological or distributional role an entity plays within a particular biogeographic context or region.
-
E.
geographicRangeTrend
Indicates how the spatial extent or distribution area of something is changing over time (e.g., expanding, contracting, or remaining stable).
- F. None of above. chosen
Provenance (4 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410fc18808190b4e47d5a71d3a126 |
completed | May 1, 2026, 2:33 a.m. |
Created at: April 18, 2026, 4:02 a.m.