Triple
T22704702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honpuku-ji |
E561417
|
entity |
| Predicate | roofTypeOfWaterTemple |
P149393
|
FINISHED |
| Object | open-to-sky pond surface |
—
|
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: open-to-sky pond surface | Statement: [Honpuku-ji, roofTypeOfWaterTemple, open-to-sky pond surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofTypeOfWaterTemple Context triple: [Honpuku-ji, roofTypeOfWaterTemple, open-to-sky pond surface]
-
A.
hasTypeOfRoof
Indicates that an entity possesses or is characterized by a specific kind or style of roof.
-
B.
hasRoofShape
Indicates that one entity possesses or is characterized by a specific shape or form of roof.
-
C.
hasIconicRoofShape
Indicates that an entity possesses a roof with a distinctive, widely recognized, or characteristic shape.
-
D.
roofStructures
Indicates a relationship where one entity consists of, includes, or is associated with roof-related structural elements of another entity.
-
E.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:16 p.m.