Triple
T36210461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial City of Buchhorn |
E1047530
|
entity |
| Predicate | presentLocationMunicipality |
P11890
|
FINISHED |
| Object | Friedrichshafen |
—
|
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: Friedrichshafen | Statement: [Imperial City of Buchhorn, presentLocationMunicipality, Friedrichshafen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentLocationMunicipality Context triple: [Imperial City of Buchhorn, presentLocationMunicipality, Friedrichshafen]
-
A.
presentDayMunicipality
chosen
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) entity.
-
B.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
C.
primaryLocationCity
Indicates the city that serves as the main or primary location associated with the subject.
-
D.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
-
E.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.