Triple
T32779811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubossary |
E838320
|
entity |
| Predicate | governedByDeJure |
P98499
|
FINISHED |
| Object | Republic of Moldova |
—
|
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: Republic of Moldova | Statement: [Dubossary, governedByDeJure, Republic of Moldova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByDeJure Context triple: [Dubossary, governedByDeJure, Republic of Moldova]
-
A.
areGovernedBy
chosen
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
B.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
C.
governedTraditionallyBy
Indicates that one entity has historically exercised customary or long-established governing authority over another entity.
-
D.
countryGovernedOnBehalfOf
Indicates that a country is administered or ruled by one party acting in the name or interest of another party.
-
E.
governedTerritoryVia
Indicates a relationship where an authority or governing body exercises control over a territory through an intermediary entity, mechanism, or arrangement.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 1, 2026, 1:14 a.m.