Triple
T19532542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 山本五十六 |
E488689
|
entity |
| Predicate | 関連地名 |
P3158
|
FINISHED |
| Object | 真珠湾 |
—
|
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: 真珠湾 | Statement: [山本五十六, 関連地名, 真珠湾]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連地名 Context triple: [山本五十六, 関連地名, 真珠湾]
-
A.
関連施設
Indicates a relationship where one facility is associated with, connected to, or otherwise related to another facility.
-
B.
hasToponymicAssociation
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
-
C.
nearbyArchipelagoNameSimilarityWith
Indicates that two archipelagos have similar or matching names and are located near each other geographically.
-
D.
relatedPlace
chosen
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
E.
typicalGeographicalAssociation
Indicates a usual or characteristic geographical connection between entities, such as a place commonly associated with a person, group, or phenomenon.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6364091f4819088b27d0ffdf6010d |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.