Triple
T22704704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honpuku-ji |
E561417
|
entity |
| Predicate | accessToMainHall |
P143167
|
FINISHED |
| Object | stairway through central opening in pond |
—
|
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: stairway through central opening in pond | Statement: [Honpuku-ji, accessToMainHall, stairway through central opening in pond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToMainHall Context triple: [Honpuku-ji, accessToMainHall, stairway through central opening in pond]
-
A.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
B.
directionFromMainHall
Indicates the spatial direction or orientation of something relative to the main hall as a reference point.
-
C.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
-
D.
interiorAccess
chosen
Indicates that one entity provides a way to enter or move within the inside space of another entity.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cdc93481908f85d04560f8c285 |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:16 p.m.