Triple
T6465869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | jingū |
E142230
|
entity |
| Predicate | architecturalTradition |
P607
|
FINISHED |
| Object | Shinto shrine architecture |
—
|
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: Shinto shrine architecture | Statement: [jingū, architecturalTradition, Shinto shrine architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalTradition Context triple: [jingū, architecturalTradition, Shinto shrine architecture]
-
A.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
-
B.
architecturalInfluence
Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
-
C.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
D.
architecturalPhilosophy
Indicates the guiding theoretical or conceptual approach that shapes how something is designed or structured architecturally.
-
E.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a1159ec81909bbfa9a9d6fa1616 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.