Triple
T22211418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokki-ji |
E548956
|
entity |
| Predicate | hasPagodaStatus |
P32932
|
FINISHED |
| Object | one of the oldest three-story pagodas in Japan |
—
|
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: one of the oldest three-story pagodas in Japan | Statement: [Hokki-ji, hasPagodaStatus, one of the oldest three-story pagodas in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPagodaStatus Context triple: [Hokki-ji, hasPagodaStatus, one of the oldest three-story pagodas in Japan]
-
A.
hasPagoda
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of a pagoda.
-
B.
eastPagodaStatus
Indicates the current condition or state of the east pagoda in relation to the context or system being described.
-
C.
hasStupa
Indicates that one entity possesses, contains, or features a stupa as part of its structure, property, or composition.
-
D.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
E.
hasChapelStatus
Indicates that an entity holds a designated status or classification specifically related to a chapel.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2bcf748190a9721f0c9ae17e70 |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.