Triple
T622371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poznań |
E14540
|
entity |
| Predicate | wasEarlyCenterOf |
P3417
|
FINISHED |
| Object | Polish statehood |
—
|
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: Polish statehood | Statement: [Poznań, wasEarlyCenterOf, Polish statehood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEarlyCenterOf Context triple: [Poznań, wasEarlyCenterOf, Polish statehood]
-
A.
wasFirstCapitalOf
Indicates that one place previously served as the earliest or original capital city of another political or administrative entity.
-
B.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
-
C.
formerCapitalOf
chosen
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
D.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
E.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e402d9c8190936896e3ebb6edc5 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.