Triple
T56801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Maize and Wheat Improvement Center |
E1123
|
entity |
| Predicate | worksIn |
P1527
|
FINISHED |
| Object | 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: developing countries | Statement: [International Maize and Wheat Improvement Center, worksIn, developing countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksIn Context triple: [International Maize and Wheat Improvement Center, worksIn, developing countries]
-
A.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
B.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
C.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
D.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
E.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.