Triple
T23071639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rynek |
E575211
|
entity |
| Predicate | isCharacteristicOfPeriod |
P114334
|
FINISHED |
| Object | medieval urban planning |
—
|
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: medieval urban planning | Statement: [Rynek, isCharacteristicOfPeriod, medieval urban planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacteristicOfPeriod Context triple: [Rynek, isCharacteristicOfPeriod, medieval urban planning]
-
A.
periodCharacterizedBy
chosen
Indicates that a specific time period is defined or distinguished by a particular characteristic, condition, or feature.
-
B.
characterInPeriod
Indicates that a character exists or is active during a specified historical or temporal period.
-
C.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
D.
reignCharacterizedBy
Indicates that a ruler’s period of governance is defined or distinguished by a particular quality, condition, or notable feature.
-
E.
settingDepictedPeriod
Indicates the historical or temporal period in which the setting of something (e.g., a work or scene) is depicted.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c5ffad881909ed626045c15dd33 |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:56 p.m.