Triple
T26551415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 福岡県太宰府市 |
E671686
|
entity |
| Predicate | 有名な寺院 |
P48433
|
FINISHED |
| Object | 観世音寺 |
—
|
NE NERFINISHED |
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: 観世音寺 | Statement: [福岡県太宰府市, 有名な寺院, 観世音寺]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 有名な寺院 Context triple: [福岡県太宰府市, 有名な寺院, 観世音寺]
-
A.
containsFamousShrine
Indicates that a location includes within its boundaries a shrine that is widely recognized or renowned.
-
B.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
C.
hasNotableTemple
chosen
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
D.
AtsutaShrineIs
Indicates that something has the status, identity, or defining characteristics of Atsuta Shrine.
-
E.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614624c80819084f6febf57f86828 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:47 a.m.