Triple
T29399085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Tenji |
E745584
|
entity |
| Predicate | formalAccessionYear |
P131810
|
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, formalAccessionYear, 668]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalAccessionYear Context triple: [Emperor Tenji, formalAccessionYear, 668]
-
A.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
-
B.
yearFormalized
chosen
Indicates the specific year in which the relationship, concept, or entity was officially established, recognized, or formalized.
-
C.
accessionAnniversaryOf
Indicates the date or event marking the anniversary of when an entity formally assumed a position, title, or membership.
-
D.
accessionPeriod
Indicates the time span during which an entity is formally acquired, admitted, or granted entry into a system, collection, or status.
-
E.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 2:49 p.m.