Triple
T21754954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thespakusatsu Gunma |
E537013
|
entity |
| Predicate | prefectureRepresentation |
P145140
|
FINISHED |
| Object | Gunma 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: Gunma Prefecture | Statement: [Thespakusatsu Gunma, prefectureRepresentation, Gunma Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefectureRepresentation Context triple: [Thespakusatsu Gunma, prefectureRepresentation, Gunma Prefecture]
-
A.
provinceRepresented
Indicates that an entity (such as a person or office) serves as the official representative of a particular province.
-
B.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
C.
governingPrefecturalCapital
Indicates that one entity serves as the administrative capital governing a particular prefecture.
-
D.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
E.
representsPoliticalEntity
Indicates that one entity serves as, or functions in the role of, a political entity in relation to another.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8d6d0081908e0ccfbccea58895 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:50 p.m.