Triple
T22868272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabala |
E567116
|
entity |
| Predicate | politicalEntityTypeOfCapital |
P78278
|
FINISHED |
| Object | kingdom |
—
|
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: kingdom | Statement: [Kabala, politicalEntityTypeOfCapital, kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalEntityTypeOfCapital Context triple: [Kabala, politicalEntityTypeOfCapital, kingdom]
-
A.
governmentTypeAsCapital
Indicates that the form or type of government is being characterized or represented as a kind of capital (e.g., political, social, or symbolic capital).
-
B.
governingTerritorialCapital
chosen
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
-
C.
countryCapitalLegislatureRelation
Indicates that a specific legislature is located in, or officially associated with, the capital city of a given country.
-
D.
coCapitalOf
Indicates that two or more cities share the status of being capital cities of the same political or administrative entity.
-
E.
countryCapitalSector
Indicates that a specified sector or area lies within or corresponds to the capital city of a given country.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f02c8b8819095cbee626f935fed |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.