Triple
T4952190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African drylands |
E111192
|
entity |
| Predicate | hasAdaptationStrategy |
P60135
|
FINISHED |
| Object | drought-resilient crops |
—
|
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-resilient crops | Statement: [African drylands, hasAdaptationStrategy, drought-resilient crops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptationStrategy Context triple: [African drylands, hasAdaptationStrategy, drought-resilient crops]
-
A.
hasMediaAdaptation
Indicates that a work has been adapted into another medium, such as film, television, or other forms of media.
-
B.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
C.
hasLiveStageAdaptation
Indicates that a work has been adapted into a live stage production, such as a play or musical.
-
D.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
E.
adaptedTo
Indicates that one entity has been modified, adjusted, or evolved to function effectively within the conditions, requirements, or characteristics defined by another entity.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b6a5d481909ad6f5e0b752496c |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6fa2d2088190ae444d3d0e47d5d2 |
completed | March 20, 2026, 4:02 p.m. |
Created at: March 20, 2026, 1:31 p.m.