Triple
T14964804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mori Arinori |
E373162
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mori |
E18131
|
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: Mori | Statement: [Mori Arinori, familyName, Mori]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mori Context triple: [Mori Arinori, familyName, Mori]
-
A.
Mori
chosen
Mori is a Japanese surname shared by various notable individuals across fields such as entertainment, sports, and politics.
-
B.
Mori
Mori is a remote Himalayan village in Uttarkashi district of Uttarakhand, India, known for its scenic beauty along the Tons River and as a base for trekking and adventure activities.
-
C.
Mori
Mori is a municipality in northern Italy’s Trentino region, known for its Alpine setting and cultural ties to its European twin towns.
-
D.
Mōri
Mōri is a prominent Japanese samurai clan that rose to power in western Honshu during the Sengoku period and later became influential daimyō under the Tokugawa shogunate.
-
E.
Murayama
Murayama is a Japanese surname borne by various notable individuals across fields such as politics, science, and the arts.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6d0487c8190b7754af8c5014b37 |
completed | April 15, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe8bdeec408190893d1db9254da24e |
completed | May 9, 2026, 1:20 a.m. |
Created at: April 10, 2026, 2:46 a.m.