Triple
T29399084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Tenji |
E745584
|
entity |
| Predicate | deFactoRuleEnd |
P61420
|
FINISHED |
| Object | 668 |
—
|
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: 668 | Statement: [Emperor Tenji, deFactoRuleEnd, 668]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoRuleEnd Context triple: [Emperor Tenji, deFactoRuleEnd, 668]
-
A.
deFactoRuleStart
Indicates the point in time or condition at which a rule begins to apply in practice, regardless of its formal or official start.
-
B.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
C.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
D.
deFactoEndOfRole
chosen
Indicates the point in time when a role effectively ended in practice, regardless of any formal or official end date.
-
E.
reasonForEndOfRule
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
- 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.