Triple
T33782274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saeki no Kuramoto |
E865687
|
entity |
| Predicate | hasHeritageSiteFounded |
P193897
|
FINISHED |
| Object | Itsukushima Shrine |
—
|
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: Itsukushima Shrine | Statement: [Saeki no Kuramoto, hasHeritageSiteFounded, Itsukushima Shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageSiteFounded Context triple: [Saeki no Kuramoto, hasHeritageSiteFounded, Itsukushima Shrine]
-
A.
foundedOnSiteOf
Indicates that something was established or built at the same physical location where another, earlier entity or structure previously existed.
-
B.
foundedCityOnSiteOf
Indicates that a city was established on the same physical location where another settlement or city previously existed.
-
C.
hasHeritageOfSite
Indicates that a site possesses or is associated with a particular heritage designation, tradition, or cultural-historical value.
-
D.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
E.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
| PDg | Predicate description generation | batch_69fd592cc56081908ce456114d407616 |
completed | May 8, 2026, 3:31 a.m. |
Created at: May 1, 2026, 1:45 a.m.