Triple
T26664384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandvikens IF |
E672139
|
entity |
| Predicate | hasHomeCityPopulation |
P144473
|
FINISHED |
| Object | approximately 25,000 (Sandviken) |
—
|
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: approximately 25,000 (Sandviken) | Statement: [Sandvikens IF, hasHomeCityPopulation, approximately 25,000 (Sandviken)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCityPopulation Context triple: [Sandvikens IF, hasHomeCityPopulation, approximately 25,000 (Sandviken)]
-
A.
hasHomeCityPopulationCharacteristic
Indicates that an entity’s home city possesses a specified population-related attribute or characteristic.
-
B.
homeCityPopulationGroup
chosen
Indicates that an entity’s home city belongs to a specified population size category or range.
-
C.
homeCityPopulationRegion
Indicates that the population of a home city falls within or is associated with a specified geographic region.
-
D.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
E.
corePopulationOf
Indicates that one entity is the primary or central population associated with, or constituting the main inhabitants of, another entity.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 3:08 a.m.