Triple
T19825509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Mountains of Jōmō |
E476313
|
entity |
| Predicate | regionSymbol |
P49410
|
FINISHED |
| Object | symbolic mountains of Gunma Prefecture |
—
|
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: symbolic mountains of Gunma Prefecture | Statement: [Three Mountains of Jōmō, regionSymbol, symbolic mountains of Gunma Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSymbol Context triple: [Three Mountains of Jōmō, regionSymbol, symbolic mountains of Gunma Prefecture]
-
A.
regionallySymbolicIn
chosen
Indicates that something serves as a symbol or emblem specifically within a particular region or geographic area.
-
B.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
C.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
D.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656c9e7348190a569a40bd1fca6ba |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.