Triple
T35840292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Town, Poznań |
E1036056
|
entity |
| Predicate | foundedAsUrbanCentre |
P55571
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Old Town, Poznań, foundedAsUrbanCentre, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsUrbanCentre Context triple: [Old Town, Poznań, foundedAsUrbanCentre, 13th century]
-
A.
foundedAsCityBy
Indicates that a city was originally established or created by a specific person, group, or authority.
-
B.
cityFoundedAround
chosen
Indicates that a city was established approximately at, but not exactly on, a specified time or period.
-
C.
foundedAsSettlementFor
Indicates that one entity was originally established specifically to serve as a settlement for another entity (such as a group, population, or community).
-
D.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
E.
foundedAsModernSettlement
Indicates that one entity was established or created as a modern-era settlement, rather than originating as an ancient or historical habitation.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:06 p.m.