Triple
T16825092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temesvár |
E408997
|
entity |
| Predicate | presentDayCityPopulationClass |
P560
|
FINISHED |
| Object | major 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: major city | Statement: [Temesvár, presentDayCityPopulationClass, major city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayCityPopulationClass Context triple: [Temesvár, presentDayCityPopulationClass, major city]
-
A.
cityPopulationContext
chosen
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
B.
currentPopulation
Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
-
C.
countryPopulationContext
Indicates the contextual population characteristics or statistics associated with a specific country.
-
D.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
E.
homeCityPopulationRegion
Indicates that the population of a home city falls within or is associated with a specified 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b310ffec81908087e5aaacc4a7c2 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.