Triple
T20515255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoori |
E503667
|
entity |
| Predicate | hasTitle |
P38
|
FINISHED |
| Object | Mikoto |
—
|
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: Mikoto | Statement: [Hoori, hasTitle, Mikoto]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikoto Context triple: [Hoori, hasTitle, Mikoto]
-
A.
Mikoto
chosen
Mikoto is a divine title associated with the Shinto moon god Tsukuyomi, reflecting reverence and honor in Japanese mythology.
-
B.
Makoto
Makoto is a common Japanese given name used for people of any gender, often associated with sincerity or truth.
-
C.
Samaru
Samaru is a prominent university town and research hub near Zaria in Kaduna State, Nigeria, best known for hosting the main campus of Ahmadu Bello University.
-
D.
Mitsuru
Mitsuru is a Japanese given name that can be used for people of any gender and is borne by various notable figures in sports, arts, and entertainment.
-
E.
Shinobu
Shinobu is a Japanese given name commonly used for both males and females and borne by various notable figures in Japanese culture.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4133048190abb777be4b65c2c4 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 11:36 a.m.