Triple
T34962684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Могилёв-Подольский |
E1008301
|
entity |
| Predicate | имеетНаселениеПорядка |
P3412
|
FINISHED |
| Object | десятки тысяч человек |
—
|
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: десятки тысяч человек | Statement: [Могилёв-Подольский, имеетНаселениеПорядка, десятки тысяч человек]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетНаселениеПорядка Context triple: [Могилёв-Подольский, имеетНаселениеПорядка, десятки тысяч человек]
-
A.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
B.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than another entity.
-
C.
hasNotablePopulation
Indicates that an entity is recognized for having a significant or noteworthy number of inhabitants or members.
-
D.
hasPopulationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
E.
populationThreshold
Indicates that a population has reached, exceeded, or fallen below a specified numerical limit used as a critical or decision-making boundary.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4 p.m.