Triple
T23938973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danjo Garan sacred precinct |
E602724
|
entity |
| Predicate | topLevelSite |
P154430
|
FINISHED |
| Object | one of the two main sacred areas of Mount Koya |
—
|
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 two main sacred areas of Mount Koya | Statement: [Danjo Garan sacred precinct, topLevelSite, one of the two main sacred areas of Mount Koya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelSite Context triple: [Danjo Garan sacred precinct, topLevelSite, one of the two main sacred areas of Mount Koya]
-
A.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
B.
typeSite
Indicates that a site is classified as being of a particular type or category.
-
C.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
D.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
E.
siteName
Indicates the name or designated title of a particular site or location associated with an entity.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa267b88190a1e7d599f22441e2 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:08 p.m.