Triple
T37069578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingo Province |
E917537
|
entity |
| Predicate | hasIchinomiya |
P106053
|
FINISHED |
| Object | Kibitsu-jinja (Bingo) |
—
|
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: Kibitsu-jinja (Bingo) | Statement: [Bingo Province, hasIchinomiya, Kibitsu-jinja (Bingo)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIchinomiya Context triple: [Bingo Province, hasIchinomiya, Kibitsu-jinja (Bingo)]
-
A.
ichinomiya
chosen
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
-
B.
hasOmamori
Indicates that one entity possesses or is associated with an omamori (a protective charm or amulet).
-
C.
hasDaishido
Indicates that an entity possesses, includes, or is associated with a Daishidō (a specific hall, building, or designated area).
-
D.
hasTorii
Indicates that something possesses or features a torii gate as part of its structure or environment.
-
E.
hasEnshrinedKami
Indicates that a shrine or sacred place contains or is dedicated to a particular kami (deity) as its enshrined object of worship.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.