Triple
T36121643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Teschinensis |
E1044757
|
entity |
| Predicate | correspondsToModernPlace |
P156663
|
FINISHED |
| Object | Cieszyn, Poland |
—
|
NE NERFINISHED |
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: Cieszyn, Poland | Statement: [Dux Teschinensis, correspondsToModernPlace, Cieszyn, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToModernPlace Context triple: [Dux Teschinensis, correspondsToModernPlace, Cieszyn, Poland]
-
A.
refersToModernCity
chosen
Indicates that one entity is a reference to, or designation for, a contemporary city in the modern world.
-
B.
modernLocationOfCity
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
-
C.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
D.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
E.
modernNameOfArea
Indicates that one area entity represents the current or modern name of another area entity.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.