Triple
T5392698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dornach |
E120369
|
entity |
| Predicate | hasPopulationUnit |
P39229
|
FINISHED |
| Object | 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: inhabitants | Statement: [Dornach, hasPopulationUnit, inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationUnit Context triple: [Dornach, hasPopulationUnit, inhabitants]
-
A.
populationUnit
chosen
Indicates the unit of measurement in which a population quantity is expressed (e.g., individuals, households, families).
-
B.
hasPopulationType
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
hasPopulationScale
Indicates the relative size or magnitude of a population associated with an entity, typically expressed as a qualitative or categorical scale.
-
E.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.