Triple
T4392805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old City of Bern |
E99404
|
entity |
| Predicate | capitalOfContext |
P37519
|
FINISHED |
| Object | capital of Switzerland |
—
|
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: capital of Switzerland | Statement: [Old City of Bern, capitalOfContext, capital of Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfContext Context triple: [Old City of Bern, capitalOfContext, capital of Switzerland]
-
A.
capitalCityContext
Indicates that one entity serves as the capital city of another entity within a specified contextual or situational framework.
-
B.
countryCapitalContext
chosen
Indicates that one entity serves as the capital city of the specified country in a given contextual or temporal setting.
-
C.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
-
D.
hostsCapitalOf
Indicates that one location serves as the capital city of another administrative or political entity.
-
E.
capitalOfFrom
Indicates that a city serves or served as the capital of a specified political entity during a particular time or from a particular source context.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a8862481909dc67abf42be6928 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.