Triple
T29399162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 額田王 |
E745586
|
entity |
| Predicate | 関連天皇 |
P79058
|
FINISHED |
| Object | 天智天皇 |
—
|
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: 天智天皇 | Statement: [額田王, 関連天皇, 天智天皇]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 関連天皇 Context triple: [額田王, 関連天皇, 天智天皇]
-
A.
就任時の天皇
Indicates the emperor who was reigning at the time someone assumed a position or office.
-
B.
退任時の天皇
Indicates the relationship in which a person holds the status of emperor at the time of their abdication or retirement from the throne.
-
C.
hasNotableEmperor
Indicates that an entity is associated with at least one emperor who is historically recognized as particularly important or distinguished.
-
D.
familyRelationToEmperor
chosen
Indicates that one entity is related to an emperor by family ties, specifying a kinship or familial connection between them.
-
E.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a055e9c8190b8e779d7f75eafa2 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:49 p.m.