Triple
T21541647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uji Bridge torii |
E531503
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ise City |
—
|
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: Ise City | Statement: [Uji Bridge torii, locatedIn, Ise City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ise City Context triple: [Uji Bridge torii, locatedIn, Ise City]
-
A.
Ise City
chosen
Ise City is a historic coastal city in central Japan best known as the home of Ise Grand Shrine, one of Shinto’s most sacred sites.
-
B.
Himeji
Himeji is a historic Japanese city best known for Himeji Castle, a UNESCO World Heritage Site and one of Japan’s most iconic and well-preserved feudal castles.
-
C.
Kakamigahara
Kakamigahara is a city in Gifu Prefecture, Japan, known for its aerospace industry, manufacturing, and proximity to Nagoya.
-
D.
Yame
Yame is a city in southwestern Japan renowned for its high-quality green tea production and traditional crafts.
-
E.
Sanjō
Sanjō was a Japanese emperor of the Heian period, remembered for his brief reign and subsequent abdication due to failing eyesight.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d12b264819096f844b5833198aa |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 16, 2026, 6:28 p.m.