Triple
T29018280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS |
E737377
|
entity |
| Predicate | benefitsFlowTo |
P487
|
FINISHED |
| Object | farmers in developing countries |
—
|
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: farmers in developing countries | Statement: [MLS, benefitsFlowTo, farmers in developing countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitsFlowTo Context triple: [MLS, benefitsFlowTo, farmers in developing countries]
-
A.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
B.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
C.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
D.
flowsUltimatelyInto
Indicates that something (typically a fluid, substance, or process) eventually moves or drains into another thing as its final destination, possibly through intermediate stages or paths.
-
E.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 9:47 a.m.