Triple
T31231226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makeyevka |
E796286
|
entity |
| Predicate | governingCountry_recognized |
P182412
|
FINISHED |
| Object | Ukraine |
—
|
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: Ukraine | Statement: [Makeyevka, governingCountry_recognized, Ukraine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingCountry_recognized Context triple: [Makeyevka, governingCountry_recognized, Ukraine]
-
A.
countryOfRecognition
Indicates the country that formally recognizes, acknowledges, or grants official status to a given entity.
-
B.
countryGovernmentRecognitionType
Indicates the type or status of official recognition that one country’s government has in relation to another state or governing authority.
-
C.
alsoRecognizedBy
Indicates that the same entity is additionally acknowledged, identified, or credited by another source, name, or authority.
-
D.
politicalRecognition
Indicates that one entity formally acknowledges the political status, authority, or legitimacy of another entity.
-
E.
recognizedByGovernment
chosen
Indicates that an entity is officially acknowledged or accepted as valid or legitimate by a governmental authority.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: April 29, 2026, 9:10 p.m.