Triple
T3794424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Górnik Łęczna |
E89733
|
entity |
| Predicate | homeCityPopulationRange |
P28398
|
FINISHED |
| Object | small town |
—
|
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: small town | Statement: [Górnik Łęczna, homeCityPopulationRange, small town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCityPopulationRange Context triple: [Górnik Łęczna, homeCityPopulationRange, small town]
-
A.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
B.
populationRange
chosen
Indicates the numerical interval within which the size of a population falls.
-
C.
populationFocus
Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
-
D.
majorPopulationIn
Indicates that a significant portion of a population is located in or primarily associated with a particular place or region.
-
E.
metropolitanAreaPopulationApproximate
Indicates that the predicate specifies an approximate total population size for a given metropolitan area.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.