Triple
T11315248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Noro |
E267948
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kure |
E498542
|
NE 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: Kure | Statement: [Mount Noro, locatedIn, Kure]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kure Context triple: [Mount Noro, locatedIn, Kure]
-
A.
Kure
chosen
Kure is a Japanese port city in Hiroshima Prefecture known historically as a major naval base and shipbuilding center.
-
B.
Toyokawa
Toyokawa is a city in Aichi Prefecture, Japan, known for its historic Toyokawa Inari temple and manufacturing industries.
-
C.
Kure Lagoon
Kure Lagoon is a shallow, sheltered body of water enclosed by the coral reef of Kure Atoll in the Northwestern Hawaiian Islands, known for its rich marine biodiversity and protected habitat.
-
D.
Natori City
Natori City is a coastal municipality in northeastern Japan known for its proximity to Sendai and its recovery efforts following the 2011 Tōhoku earthquake and tsunami.
-
E.
Kure District
Kure District is a major regional command of the Japan Maritime Self-Defense Force responsible for naval operations and support in the western part of Japan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c2c7b081909af8acebc8aa93aa |
completed | April 9, 2026, 6:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58b4ec4ac81908d51e3815a054704 |
completed | April 20, 2026, 2:11 a.m. |
Created at: April 8, 2026, 9:32 p.m.