Triple
T563118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lwów |
E13495
|
entity |
| Predicate | historicalPopulationGroup |
P3032
|
FINISHED |
| Object | Poles |
—
|
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: Poles | Statement: [Lwów, historicalPopulationGroup, Poles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPopulationGroup Context triple: [Lwów, historicalPopulationGroup, Poles]
-
A.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
B.
demographicScope
Indicates the specific population group or demographic segment to which something (e.g., a policy, study, product, or service) is targeted or applicable.
-
C.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
D.
hasSignificantPopulationGroup
Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
-
E.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a712bc48190ba298b3c76ab11cc |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.