Triple
T4038947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prešov |
E83895
|
entity |
| Predicate | populationRankInSlovakia |
P25930
|
FINISHED |
| Object | third largest city |
—
|
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: third largest city | Statement: [Prešov, populationRankInSlovakia, third largest city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInSlovakia Context triple: [Prešov, populationRankInSlovakia, third largest city]
-
A.
populationRankInUkraine
Indicates the relative position of an entity in terms of population size compared to other entities within Ukraine.
-
B.
populationRankAfter
Indicates the relative position of an entity in a population-based ordering that comes after another entity’s population rank.
-
C.
populationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
D.
populationRankInLithuania
Indicates the relative position of an entity in terms of population size compared to other entities within Lithuania.
-
E.
hasPopulationRankInRegion
chosen
Indicates that an entity has a specific population-based rank or position within a defined geographic region.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb37e24c81908d6357ab8ba5388d |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.