Triple
T30641523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza coarctata |
E779991
|
entity |
| Predicate | toleranceTo |
P582
|
FINISHED |
| Object | high salinity |
—
|
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: high salinity | Statement: [Oryza coarctata, toleranceTo, high salinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toleranceTo Context triple: [Oryza coarctata, toleranceTo, high salinity]
-
A.
tolerates
chosen
Indicates that one entity endures, accepts, or allows the presence, behavior, or condition of another entity without intervening to stop or change it.
-
B.
transportTolerance
Indicates the degree to which an entity can withstand or remain functional under the conditions and stresses of being transported.
-
C.
confinementTolerance
Indicates the degree to which an entity can endure or function effectively under restricted, enclosed, or limited-movement conditions.
-
D.
leniencyLevel
Indicates the degree of tolerance, forgiveness, or permissiveness applied in judging or responding to an action or behavior.
-
E.
toleranceToLocalStresses
Indicates the degree to which an entity can withstand or adapt to stresses or pressures arising from its immediate local environment.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a557e308190a55aa6958b6d012e |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.