Triple
T23664565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirishima Shrine |
E584540
|
entity |
| Predicate | hasMainHallStyle |
P14461
|
FINISHED |
| Object | nagare-zukuri |
—
|
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: nagare-zukuri | Statement: [Kirishima Shrine, hasMainHallStyle, nagare-zukuri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainHallStyle Context triple: [Kirishima Shrine, hasMainHallStyle, nagare-zukuri]
-
A.
hasMainHallType
chosen
Indicates the specific category or kind of main hall associated with an entity.
-
B.
hasMainHallShape
Indicates that an entity’s main hall has a specific geometric or structural shape.
-
C.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
-
D.
hasReceptionHall
Indicates that one entity possesses or includes a reception hall as part of its facilities or structure.
-
E.
hasGrandHall
Indicates that an entity possesses or includes a grand hall as part of its structure or facilities.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40ad45c8190a3a0ae7c7f9bf3a5 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.