Triple
T28426965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usa Hachiman-gū |
E720106
|
entity |
| Predicate | belongsToShrineCategory |
P182283
|
FINISHED |
| Object | Kanpei-taisha |
—
|
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: Kanpei-taisha | Statement: [Usa Hachiman-gū, belongsToShrineCategory, Kanpei-taisha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToShrineCategory Context triple: [Usa Hachiman-gū, belongsToShrineCategory, Kanpei-taisha]
-
A.
hasShrineCategory
chosen
Indicates that an entity is associated with a specific category or type of shrine.
-
B.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
C.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
-
D.
recognizedAsShrineBy
Indicates that something is regarded or designated as a shrine by a particular person, group, or authority.
-
E.
associatedShrineComplex
Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 28, 2026, 1:37 a.m.