Triple
T22787827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honpukuji temple complex |
E564017
|
entity |
| Predicate | featureOfWaterTemple |
P20923
|
FINISHED |
| Object | large reflecting pool |
—
|
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: large reflecting pool | Statement: [Honpukuji temple complex, featureOfWaterTemple, large reflecting pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureOfWaterTemple Context triple: [Honpukuji temple complex, featureOfWaterTemple, large reflecting pool]
-
A.
roofTypeOfWaterTemple
Indicates the specific style or type of roof that characterizes a given water temple.
-
B.
typicalShrineFeature
Indicates that something is a characteristic or commonly found element of a shrine.
-
C.
completionDateOfWaterTemple
Indicates the date on which the construction or development of the water temple was completed.
-
D.
waterFeature
chosen
Indicates the presence of a natural or artificial body or flow of water associated with the subject.
-
E.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c32de6481909ef358d16de98496 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.