Triple
T30182406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rauma |
E767237
|
entity |
| Predicate | numberOfInhabitants |
P190478
|
FINISHED |
| Object | about 800 |
—
|
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: about 800 | Statement: [Old Rauma, numberOfInhabitants, about 800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInhabitants Context triple: [Old Rauma, numberOfInhabitants, about 800]
-
A.
hasPopulationOf
chosen
Indicates that an entity possesses a specific number of inhabitants or residents as its population.
-
B.
corePopulationOf
Indicates that one entity is the primary or central population associated with, or constituting the main inhabitants of, another entity.
-
C.
hostsPopulation
Indicates that an entity serves as the living environment or container in which a particular population exists or resides.
-
D.
languageInhabitants
Indicates that a particular language is spoken or used by the inhabitants of a specified place or region.
-
E.
populationCountedIn
Indicates that the population of one entity is measured, recorded, or included within the population statistics 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
Created at: April 29, 2026, 7:26 p.m.