Triple
T33782245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinden-zukuri |
E865686
|
entity |
| Predicate | typicalPlanElement |
—
|
GENERATED |
| Object | north-south axis orientation |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlanElement Context triple: [Shinden-zukuri, typicalPlanElement, north-south axis orientation]
-
A.
hasTypicalPlan
Indicates that there is a standard or commonly followed plan, procedure, or course of action typically associated with the given entity or situation.
-
B.
managementPlanSpecifies
Indicates that a management plan explicitly defines or details specific actions, procedures, or conditions to be followed.
-
C.
typicalProgramElement
Indicates that one program element is a representative or characteristic example of another program element or category of elements.
-
D.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
- F. None of above. chosen
Provenance (1 batch)
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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.