Triple
T35358552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conocarpus |
E1021404
|
entity |
| Predicate | Conocarpus erectus_habitat |
P183273
|
FINISHED |
| Object | coastal mangroves |
—
|
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: coastal mangroves | Statement: [Conocarpus, Conocarpus erectus_habitat, coastal mangroves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Conocarpus erectus_habitat Context triple: [Conocarpus, Conocarpus erectus_habitat, coastal mangroves]
-
A.
Conocarpus erectus_commonName
Indicates that a common (vernacular) name is assigned to the species Conocarpus erectus.
-
B.
hasMangroveInfluence
Indicates that one entity exerts ecological, environmental, or functional influence on another due to the presence or effects of mangrove ecosystems.
-
C.
hasMangroveArea
Indicates that an entity possesses or includes an area covered or characterized by mangrove vegetation.
-
D.
includesEpiphytes
Indicates that something contains or supports the presence of epiphytic organisms as part of it or within it.
-
E.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
- 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_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:03 p.m.