Triple
T29356133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naha–Tokyo Haneda |
E744447
|
entity |
| Predicate | locatedInPrefectureOfOrigin |
P17718
|
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, locatedInPrefectureOfOrigin, Okinawa Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPrefectureOfOrigin Context triple: [Naha–Tokyo Haneda, locatedInPrefectureOfOrigin, Okinawa Prefecture]
-
A.
locatedInRegionOfPrefecture
Indicates that one entity is geographically situated within a specific region that belongs to or is administered as part of a given prefecture.
-
B.
locatedInPrefectureLevel
Indicates that one entity is geographically situated within, and administratively belongs to, a specific prefecture-level jurisdiction.
-
C.
homePrefecture
chosen
Indicates the prefecture that an entity considers its home or place of origin.
-
D.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
E.
hostPrefecture
Indicates the prefecture that serves as the host location for an event, activity, or 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: April 28, 2026, 2:12 p.m.