Triple
T2561103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volga Germans |
E57241
|
entity |
| Predicate | historicalPopulationPeakCentury |
P29980
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Volga Germans, historicalPopulationPeakCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPopulationPeakCentury Context triple: [Volga Germans, historicalPopulationPeakCentury, 19th century]
-
A.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
B.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
C.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
D.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
E.
flourishedToCentury
chosen
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.