Triple
T9550088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine and Moldova |
E230398
|
entity |
| Predicate | shareEconomicSectors |
P47145
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Ukraine and Moldova, shareEconomicSectors, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareEconomicSectors Context triple: [Ukraine and Moldova, shareEconomicSectors, agriculture]
-
A.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
B.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
economicClassification
Indicates how an entity is categorized based on its economic characteristics, status, or role within an economic system.
-
E.
associatedWithEconomicSector
chosen
Indicates that an entity has a connection or involvement with a particular economic sector, such as operating, participating, or being relevant within that sector.
- 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_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. |
Created at: March 30, 2026, 8:02 p.m.