Triple
T14123073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Reception Rooms |
E339949
|
entity |
| Predicate | cityCapitalOf |
P35753
|
FINISHED |
| Object | Copenhagen, capital of Denmark |
—
|
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: Copenhagen, capital of Denmark | Statement: [Royal Reception Rooms, cityCapitalOf, Copenhagen, capital of Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCapitalOf Context triple: [Royal Reception Rooms, cityCapitalOf, Copenhagen, capital of Denmark]
-
A.
cityAsCapitalOf
chosen
Indicates that a city serves as the official capital of a specified political or administrative entity.
-
B.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
C.
countryCapitalFunction
Indicates that one entity functions as the capital city of a given country.
-
D.
countryCapitalContext
Indicates that one entity serves as the capital city of the specified country in a given contextual or temporal setting.
-
E.
countryCapitalOf
Indicates that a country serves as the capital location for a specified political or geographic entity.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6095548881908a9e66adccca92d2 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.