Triple
T38173886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lecythidaceae |
E1000150
|
entity |
| Predicate | regionRichness |
P20376
|
FINISHED |
| Object | Amazon Basin |
—
|
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: Amazon Basin | Statement: [Lecythidaceae, regionRichness, Amazon Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionRichness Context triple: [Lecythidaceae, regionRichness, Amazon Basin]
-
A.
richness
Indicates that an entity possesses a high degree of abundance, complexity, or density in some valued attribute or resource.
-
B.
derivesRichnessFrom
Indicates that one entity obtains or enhances its richness, depth, or complexity as a result of another entity.
-
C.
regionStrength
Indicates the relative level of influence, power, or dominance that one region holds within a specified context or comparison.
-
D.
richIn
chosen
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
E.
governsRegionRichIn
Indicates that an entity exercises governing authority over a region characterized by abundant resources or wealth.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 3, 2026, 4:29 p.m.