Triple
T30067346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takamatsu Castle |
E764068
|
entity |
| Predicate | prefectureCapitalContext |
P14967
|
FINISHED |
| Object | Takamatsu is capital of Kagawa Prefecture |
—
|
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: Takamatsu is capital of Kagawa Prefecture | Statement: [Takamatsu Castle, prefectureCapitalContext, Takamatsu is capital of Kagawa Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefectureCapitalContext Context triple: [Takamatsu Castle, prefectureCapitalContext, Takamatsu is capital of Kagawa Prefecture]
-
A.
prefectureCapital
chosen
Indicates that a city serves as the administrative capital of a given prefecture.
-
B.
governingPrefecturalCapital
Indicates that one entity serves as the administrative capital governing a particular prefecture.
-
C.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
D.
prefectureCapitalRegion
Indicates that a region serves as the capital administrative area within a prefecture.
-
E.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca767788190abd71ea33ce049e5 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:59 p.m.