Triple
T32335168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenach-Erfurt |
E826151
|
entity |
| Predicate | hasCityInTerritory |
P70992
|
FINISHED |
| Object | Eisenach |
—
|
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: Eisenach | Statement: [Eisenach-Erfurt, hasCityInTerritory, Eisenach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityInTerritory Context triple: [Eisenach-Erfurt, hasCityInTerritory, Eisenach]
-
A.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
-
B.
isCityOf
chosen
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
C.
hasCapitalCityWithin
Indicates that a specified capital city is geographically located within the boundaries of a given region or country.
-
D.
isPartOfCapitalCityOf
Indicates that something is a constituent or component of the capital city belonging to a particular political or administrative entity.
-
E.
isProvincialCityOf
Indicates that a city serves as an administrative or officially designated city within a specified province.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 12:48 a.m.