Triple
T26013232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serranía de la Macarena |
E646955
|
entity |
| Predicate | floraRegion |
P150308
|
FINISHED |
| Object | Orinoco flora |
—
|
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: Orinoco flora | Statement: [Serranía de la Macarena, floraRegion, Orinoco flora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraRegion Context triple: [Serranía de la Macarena, floraRegion, Orinoco flora]
-
A.
hasFloristicRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a particular floristic (plant-distribution) region.
-
B.
hasFloristicSubregion
Indicates that a region is part of, or contained within, a more specific floristic subregion in terms of its plant composition or flora classification.
-
C.
hasFloralRegion
Indicates that one entity possesses or is associated with a specific floral region as a characteristic or component.
-
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.
hasRegionalFlower
Indicates that a region is associated with a specific flower designated as its symbolic or representative flower.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 9:02 a.m.