Triple
T23626857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ito District, Wakayama Prefecture |
E583490
|
entity |
| Predicate | containsNotablePlace |
P153329
|
FINISHED |
| Object | Mount Koya |
—
|
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: Mount Koya | Statement: [Ito District, Wakayama Prefecture, containsNotablePlace, Mount Koya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsNotablePlace Context triple: [Ito District, Wakayama Prefecture, containsNotablePlace, Mount Koya]
-
A.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
B.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
C.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
D.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
E.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17d4f508190abbb508746bfebb9 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:46 p.m.