Triple
T35948514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brachysiphon |
E1039650
|
entity |
| Predicate | ecologicalRegion |
P948
|
FINISHED |
| Object | Afrotropical realm |
—
|
NE NERFINISHED |
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: Afrotropical realm | Statement: [Brachysiphon, ecologicalRegion, Afrotropical realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecologicalRegion Context triple: [Brachysiphon, ecologicalRegion, Afrotropical realm]
-
A.
ecoregion
chosen
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
B.
ecoregionName
Indicates the specific named ecoregion to which an entity or location belongs.
-
C.
ecozone
Indicates that two entities stand in a biogeographical relationship where one is an ecological zone (ecozone) that characterizes or contains the other.
-
D.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
E.
ecoregionsInclude
Indicates that one ecoregion spatially contains or encompasses another ecoregion or area within its boundaries.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.