Triple
T2619228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transnistria |
E58963
|
entity |
| Predicate | hasEthnicallyMixedPopulation |
P42257
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Transnistria, hasEthnicallyMixedPopulation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicallyMixedPopulation Context triple: [Transnistria, hasEthnicallyMixedPopulation, true]
-
A.
hasSignificantPopulationGroup
Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
-
B.
numberOfEthnicGroupsRepresented
Indicates the count of distinct ethnic groups that are present or represented in a given context or entity.
-
C.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
-
D.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
-
E.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abdac82b688190886a6ec2d6e2abc7 |
completed | March 7, 2026, 7:59 a.m. |
Created at: March 6, 2026, 9:50 p.m.