Triple
T21819495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outer Shrine |
E538686
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ise |
—
|
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 | Statement: [Outer Shrine, locatedIn, Ise]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ise Context triple: [Outer Shrine, locatedIn, Ise]
-
A.
Ise
chosen
Ise is a Japanese city in Mie Prefecture best known as the site of Ise Grand Shrine, the most sacred Shinto shrine dedicated to the sun goddess Amaterasu.
-
B.
Ise
The Ise is a river in Lower Saxony, Germany, known as a tributary of the Aller and part of the Weser river system.
-
C.
Ise
Ise was a Japanese Imperial Navy battleship later converted into a hybrid battleship–aircraft carrier during World War II.
-
D.
Ise
Ise was a prominent early Heian-period Japanese waka poet and court lady, celebrated for her romantic and elegant poetry preserved in imperial anthologies.
-
E.
Ise
Ise is the original family name of Hōjō Sōun, a prominent Sengoku-period samurai and feudal lord who founded the Later Hōjō clan in Japan.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cce0b8081909e20ded72db40304 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 16, 2026, 6:54 p.m.