Triple
T28632989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka–Tokyo Haneda |
E724694
|
entity |
| Predicate | terminalCityRegion |
P170669
|
FINISHED |
| Object | Fukuoka 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: Fukuoka Prefecture | Statement: [Fukuoka–Tokyo Haneda, terminalCityRegion, Fukuoka Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalCityRegion Context triple: [Fukuoka–Tokyo Haneda, terminalCityRegion, Fukuoka Prefecture]
-
A.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
B.
hostCityRegion
Indicates the city or broader region that serves as the host location for a specified event or entity.
-
C.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
-
D.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
-
E.
regionOfTheReferredCity
Indicates that one entity is the geographic or administrative region in which the referenced city is located.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 28, 2026, 4:38 a.m.