Triple
T5789027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosenborg BK |
E128344
|
entity |
| Predicate | homeCityPopulationCategory |
P12871
|
FINISHED |
| Object | major Norwegian 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 Norwegian city | Statement: [Rosenborg BK, homeCityPopulationCategory, major Norwegian city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCityPopulationCategory Context triple: [Rosenborg BK, homeCityPopulationCategory, major Norwegian city]
-
A.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
B.
homeCityPopulationRole
Indicates that an entity’s role or status is defined in relation to the population size of its home city.
-
C.
populationHubFor
Indicates a location that serves as a central concentration point or primary center for a population.
-
D.
populationFocus
Indicates that something is primarily directed toward, concerned with, or designed for a particular population or demographic group.
-
E.
majorPopulationCenter
chosen
Indicates that a location functions as a primary hub of population concentration and activity within a 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a53d0148190bdebc4f5609939ac |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.