Triple
T20145513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 元興寺 |
E491291
|
entity |
| Predicate | 関連遺跡 |
P78887
|
FINISHED |
| Object | 元興寺塔跡 |
—
|
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: 元興寺塔跡 | Statement: [元興寺, 関連遺跡, 元興寺塔跡]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連遺跡 Context triple: [元興寺, 関連遺跡, 元興寺塔跡]
-
A.
relatedToArchaeologicalSite
chosen
Indicates that one entity has a contextual, historical, or functional connection to an archaeological site.
-
B.
heritageSiteAssociatedWith
Indicates a relationship where a heritage site is connected or linked to another entity, such as a person, event, culture, or location, through historical, cultural, or symbolic association.
-
C.
関連施設
Indicates a relationship where one facility is associated with, connected to, or otherwise related to another facility.
-
D.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
E.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679e43a48190b3a5da5710b07ff7 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.