Triple
T35358555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conocarpus |
E1021404
|
entity |
| Predicate | Conocarpus lancifolius_nativeRange |
P184049
|
FINISHED |
| Object | Horn of Africa |
—
|
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: Horn of Africa | Statement: [Conocarpus, Conocarpus lancifolius_nativeRange, Horn of Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Conocarpus lancifolius_nativeRange Context triple: [Conocarpus, Conocarpus lancifolius_nativeRange, Horn of Africa]
-
A.
Conocarpus erectus_nativeRange
Indicates that the native geographic range or region where *Conocarpus erectus* naturally occurs is the specified place.
-
B.
Conocarpus erectus_commonName
Indicates that a common (vernacular) name is assigned to the species Conocarpus erectus.
-
C.
Conocarpus erectus_habitat
Indicates the type of environment or habitat in which *Conocarpus erectus* naturally occurs or is typically found.
-
D.
hasMangroveArea
Indicates that an entity possesses or includes an area covered or characterized by mangrove vegetation.
-
E.
hasMangroveInfluence
Indicates that one entity exerts ecological, environmental, or functional influence on another due to the presence or effects of mangrove ecosystems.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.