Triple
T1927961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itami |
E40874
|
entity |
| Predicate | regionServedByAirport |
P4363
|
FINISHED |
| Object | Kansai region |
—
|
LITERAL FINISHED |
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: Kansai region | Statement: [Itami, regionServedByAirport, Kansai region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionServedByAirport Context triple: [Itami, regionServedByAirport, Kansai region]
-
A.
airportServed
chosen
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
-
B.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
C.
airlineServiceArea
Indicates the geographic regions or locations where an airline operates or provides service.
-
D.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
E.
otherRegionalAirports
Indicates that the entities are airports located in different regions from each other but considered as alternative or comparable regional airports.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb263cdb8819084d0bda98a2a71e0 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.