Triple
T5219089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berner |
E117823
|
entity |
| Predicate | countryCapitalAssociation |
P62098
|
FINISHED |
| Object | resident of the federal city 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: resident of the federal city of Switzerland | Statement: [Berner, countryCapitalAssociation, resident of the federal city of Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalAssociation Context triple: [Berner, countryCapitalAssociation, resident of the federal city of Switzerland]
-
A.
countryCapitalOf
Indicates that a country serves as the capital location for a specified political or geographic entity.
-
B.
countryCapitalContext
Indicates that one entity serves as the capital city of the specified country in a given contextual or temporal setting.
-
C.
countryCapitalLocatedIn
Indicates that the capital city of a country is geographically situated within that country.
-
D.
countryCapitalFunction
Indicates that one entity functions as the capital city of a given country.
-
E.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
- F. None of above. chosen
Provenance (4 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ab6e63c8190964b2b65a0206134 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.