Triple
T33329558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 仁徳天皇 |
E853363
|
entity |
| Predicate | 陵墓規模 |
P68077
|
FINISHED |
| Object | 世界最大級の墳墓とされる古墳に葬られたと伝えられる |
—
|
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: 世界最大級の墳墓とされる古墳に葬られたと伝えられる | Statement: [仁徳天皇, 陵墓規模, 世界最大級の墳墓とされる古墳に葬られたと伝えられる]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 陵墓規模 Context triple: [仁徳天皇, 陵墓規模, 世界最大級の墳墓とされる古墳に葬られたと伝えられる]
-
A.
burialGroundCapacity
Indicates the maximum number of burials or remains that a burial ground is designed or allowed to accommodate.
-
B.
hasNumberOfMonumentalTombs
Indicates the specific count of monumental tombs associated with an entity.
-
C.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
D.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
E.
burialSiteFeature
chosen
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.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.