Triple
T22473422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuradaceae |
E555562
|
entity |
| Predicate | ecologicalAdaptation |
P130825
|
FINISHED |
| Object | drought tolerance |
—
|
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: drought tolerance | Statement: [Neuradaceae, ecologicalAdaptation, drought tolerance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecologicalAdaptation Context triple: [Neuradaceae, ecologicalAdaptation, drought tolerance]
-
A.
typicalVegetationAdaptation
chosen
Indicates the characteristic ways in which vegetation is adapted to the prevailing environmental conditions of a given area.
-
B.
regionOfAdaptation
Indicates the geographic or environmental region to which an entity is specifically adapted.
-
C.
ecologicalRelevance
Indicates that one entity has significance, impact, or importance for the functioning, stability, or dynamics of another entity’s ecosystem or ecological context.
-
D.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
E.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be2034c81909d1263f2ed114b46 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.