Triple
T21359464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munakata Taisha |
E526730
|
entity |
| Predicate | hasSacredIsland |
P970
|
FINISHED |
| Object | Okinoshima |
—
|
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: Okinoshima | Statement: [Munakata Taisha, hasSacredIsland, Okinoshima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredIsland Context triple: [Munakata Taisha, hasSacredIsland, Okinoshima]
-
A.
hasIsland
chosen
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
B.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
C.
hasIslandArc
Indicates that one geographic or geological entity possesses or is associated with an island arc feature.
-
D.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
E.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5bac9e1481909121e89f046c77f6 |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:07 p.m.