Triple
T37341200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenpyō-kanpō |
E927041
|
entity |
| Predicate | namedDuringReignOf |
P194044
|
FINISHED |
| Object | Emperor Shōmu |
—
|
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: Emperor Shōmu | Statement: [Tenpyō-kanpō, namedDuringReignOf, Emperor Shōmu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedDuringReignOf Context triple: [Tenpyō-kanpō, namedDuringReignOf, Emperor Shōmu]
-
A.
heldDuringReignOf
Indicates that a role, position, or status was held by someone during the period when a particular ruler or authority was in power.
-
B.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
-
C.
builtDuringReignOf
Indicates that something was constructed while a particular ruler or authority was in power.
-
D.
modifiedDuringReignOf
Indicates that an entity was altered, updated, or changed while a particular ruler or authority was in power.
-
E.
attainedUnderReignOf
Indicates that something (such as a status, title, or achievement) was obtained or realized during the period when a particular ruler or authority was in power.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: May 3, 2026, 4:16 p.m.