Triple
T455872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musashi Imperial Graveyard |
E7230
|
entity |
| Predicate | hasGraveType |
P6490
|
FINISHED |
| Object | mausoleum |
—
|
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: mausoleum | Statement: [Musashi Imperial Graveyard, hasGraveType, mausoleum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGraveType Context triple: [Musashi Imperial Graveyard, hasGraveType, mausoleum]
-
A.
hasTypeOfBurial
chosen
Indicates the specific kind or method of burial associated with an entity.
-
B.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
C.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
D.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef9f772c8190863399c5ee1378fe |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.