Triple
T29356135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naha–Tokyo Haneda |
E744447
|
entity |
| Predicate | originCityIsCapitalOfPrefecture |
P14967
|
FINISHED |
| Object | Okinawa 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: Okinawa Prefecture | Statement: [Naha–Tokyo Haneda, originCityIsCapitalOfPrefecture, Okinawa Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originCityIsCapitalOfPrefecture Context triple: [Naha–Tokyo Haneda, originCityIsCapitalOfPrefecture, Okinawa Prefecture]
-
A.
isPrefecturalCityOf
Indicates that a city holds the administrative status of a prefecture-level city within a given region or country.
-
B.
prefectureCapital
chosen
Indicates that a city serves as the administrative capital of a given prefecture.
-
C.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
D.
isInPrefecturalCapital
Indicates that one entity is located within the administrative boundaries of a prefectural capital city.
-
E.
governingPrefecturalCapital
Indicates that one entity serves as the administrative capital governing a particular 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: April 28, 2026, 2:12 p.m.