Triple
T25752282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radun |
E648496
|
entity |
| Predicate | locatedInCountryOfPrimaryAssociation |
P79579
|
FINISHED |
| Object | Belarus |
—
|
NE NERFINISHED |
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: Belarus | Statement: [Radun, locatedInCountryOfPrimaryAssociation, Belarus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryOfPrimaryAssociation Context triple: [Radun, locatedInCountryOfPrimaryAssociation, Belarus]
-
A.
countryOfStrongAssociation
Indicates a strong, notable, or primary connection between an entity and a specific country, such as origin, major activity, or significant influence.
-
B.
primaryLocationCountry
chosen
Indicates the country that serves as the main or primary location associated with the subject.
-
C.
locatedInCountryOfOperatedVenue
Indicates that an entity is situated within the country where a related venue operates.
-
D.
designationCountry
Indicates the country that officially assigns or confers a particular status, title, or designation on an entity.
-
E.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 22, 2026, 4:36 a.m.