Triple
T19698026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komatsu Airport |
E473014
|
entity |
| Predicate | locatedInCity |
P40
|
FINISHED |
| Object | Komatsu |
—
|
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: Komatsu | Statement: [Komatsu Airport, locatedInCity, Komatsu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Komatsu Context triple: [Komatsu Airport, locatedInCity, Komatsu]
-
A.
Komatsu
chosen
Komatsu is a city in Ishikawa Prefecture, Japan, known for its manufacturing industry and as the namesake of the global construction equipment company Komatsu Ltd.
-
B.
Kamiyama
Kamiyama is a Japanese surname borne by various individuals, including artists, athletes, and public figures.
-
C.
Koyama
Koyama is a Japanese surname borne by various notable individuals across fields such as entertainment, sports, and the arts.
-
D.
Kominato
Kominato is a coastal area in present-day Chiba Prefecture, Japan, historically known as the birthplace of the Buddhist monk Nichiren.
-
E.
Takamado
Takamado is a Japanese imperial family name most prominently associated with the late Prince Takamado and his descendants, a branch of Japan’s royal household.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b2baec81909ee2cd6ead632836 |
completed | April 20, 2026, 3:13 p.m. |
Created at: April 10, 2026, 1:46 p.m.