Triple
T11433909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Shōmu |
E270955
|
entity |
| Predicate | laterLifeRole |
P81335
|
FINISHED |
| Object | Buddhist monk |
—
|
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: Buddhist monk | Statement: [Emperor Shōmu, laterLifeRole, Buddhist monk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLifeRole Context triple: [Emperor Shōmu, laterLifeRole, Buddhist monk]
-
A.
roleAfterRetirement
Indicates the position, function, or status an entity assumes after it has retired from its previous role or activity.
-
B.
laterLifeEvent
Indicates that one event, condition, or action occurs during a later stage in an entity’s life relative to earlier life phases.
-
C.
laterLifePractice
chosen
Indicates that an individual engaged in a particular activity, role, or practice during the later period of their life.
-
D.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
-
E.
turnedSenior
Indicates that an entity has transitioned into senior status or a senior role relative to a previous state or position.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c485f481909dd3d9b0993f3faf |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.