Triple
T9550079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine and Moldova |
E230398
|
entity |
| Predicate | haveAgriculturalTrade |
P89745
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ukraine and Moldova, haveAgriculturalTrade, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveAgriculturalTrade Context triple: [Ukraine and Moldova, haveAgriculturalTrade, yes]
-
A.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
-
B.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
C.
representsAgriculture
Indicates that one entity serves as an example, instance, or embodiment of agriculture in relation to another entity.
-
D.
agriculturalProduce
Indicates that one entity is an agricultural product (such as crops or livestock-derived goods) produced by or associated with another entity.
-
E.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9906bc90819086f105c453e63c83 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:02 p.m.