Triple
T10238900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Nintoku |
E243537
|
entity |
| Predicate | burialMoundType |
P89755
|
FINISHED |
| Object | keyhole-shaped kofun |
—
|
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: keyhole-shaped kofun | Statement: [Emperor Nintoku, burialMoundType, keyhole-shaped kofun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialMoundType Context triple: [Emperor Nintoku, burialMoundType, keyhole-shaped kofun]
-
A.
primaryMoundType
chosen
Indicates the main or dominant type of mound associated with or characterizing an entity.
-
B.
archaeologicalMoundName
Indicates the specific name assigned to an archaeological mound in which something is located, associated, or from which it originates.
-
C.
burialSiteFeature
Indicates a specific physical characteristic or element associated with a burial site, such as structures, markers, or other notable features present at the place of interment.
-
D.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
E.
hasArchaeologicalMound
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:23 a.m.