Triple
T35368275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Saxe-Weimar-Eisenach |
E1021696
|
entity |
| Predicate | centralCityOfTerritory |
P20536
|
FINISHED |
| Object | Weimar |
—
|
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: Weimar | Statement: [Duke of Saxe-Weimar-Eisenach, centralCityOfTerritory, Weimar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCityOfTerritory Context triple: [Duke of Saxe-Weimar-Eisenach, centralCityOfTerritory, Weimar]
-
A.
mainCityInTerritory
Indicates that a city serves as the primary or most important urban center within a specified territory.
-
B.
capitalRegionOf
Indicates that one region serves as the capital or primary administrative center of another region.
-
C.
capitalCityOfJurisdiction
Indicates that one entity is the primary city serving as the official capital of the specified jurisdiction or governing region.
-
D.
capitalCityOfStateLocatedIn
Indicates that a city serves as the capital of a state, and that state is located within a specified larger geographic or political region.
-
E.
territorialCapital
chosen
Indicates that a location serves as the administrative or political capital of a defined territory or region.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:03 p.m.