Triple
T35612107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zadran District |
E1029062
|
entity |
| Predicate | populationEstimateUnit |
P39229
|
FINISHED |
| Object | people |
—
|
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: people | Statement: [Zadran District, populationEstimateUnit, people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationEstimateUnit Context triple: [Zadran District, populationEstimateUnit, people]
-
A.
populationUnit
chosen
Indicates the unit of measurement in which a population quantity is expressed (e.g., individuals, households, families).
-
B.
populationCensusUnit
Indicates that a population count or demographic measurement is taken with respect to a specific census-defined unit or area.
-
C.
hasPopulationDensityUnit
Indicates the unit of measurement used to express a population density value for a given entity.
-
D.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
E.
populationEstimateLoss
Indicates a reduction or decrease in a previously estimated population size.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:05 p.m.