Triple
T18231998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akagi Daimyōjin |
E436563
|
entity |
| Predicate | hasShrineStatus |
P92982
|
FINISHED |
| Object | principal deity of Akagi Shrine |
—
|
LITERAL FINISHED |
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: principal deity of Akagi Shrine | Statement: [Akagi Daimyōjin, hasShrineStatus, principal deity of Akagi Shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShrineStatus Context triple: [Akagi Daimyōjin, hasShrineStatus, principal deity of Akagi Shrine]
-
A.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
-
B.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
C.
hasShrineTitle
chosen
Indicates that an entity holds or is associated with a specific honorific or formal title used in the context of a shrine.
-
D.
hasInnerShrine
Indicates that one entity contains or includes another entity that functions as an inner shrine within it.
-
E.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b414308190bc7dd8e73c0a362c |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.