Triple
T30012349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Útica |
E762499
|
entity |
| Predicate | demographicsPopulation |
P328
|
FINISHED |
| Object | a few thousand inhabitants |
—
|
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: a few thousand inhabitants | Statement: [Útica, demographicsPopulation, a few thousand inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicsPopulation Context triple: [Útica, demographicsPopulation, a few thousand inhabitants]
-
A.
demographics
Indicates the relationship of providing or characterizing statistical information about a population’s attributes, such as age, gender, income, or education.
-
B.
population
chosen
Indicates the total number of individuals living in or present within a specified area or group.
-
C.
populationDemonym
Indicates the term used to refer to the people or inhabitants associated with a particular place or region.
-
D.
corePopulationOf
Indicates that one entity is the primary or central population associated with, or constituting the main inhabitants of, another entity.
-
E.
demographicsIn
Indicates that demographic information is associated with or applies within a specified geographic or organizational 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679818b0881909ccad238465fdf51 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:44 p.m.