Triple
T36068759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daiji |
E1043307
|
entity |
| Predicate | eraStartReason |
P153523
|
FINISHED |
| Object | change of era name to mark an event or series of events |
—
|
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: change of era name to mark an event or series of events | Statement: [Daiji, eraStartReason, change of era name to mark an event or series of events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraStartReason Context triple: [Daiji, eraStartReason, change of era name to mark an event or series of events]
-
A.
eraStart
Indicates the point in time at which a particular era or period begins.
-
B.
eraStartLocation
Indicates the place where a particular era or time period begins or is initiated.
-
C.
initiatedBecauseOf
chosen
Indicates that one event, action, or process was started as a direct result of, or in response to, another specified cause or condition.
-
D.
eraEnd
Indicates the point in time or event at which a particular era, period, or phase comes to a close.
-
E.
eraBefore
Indicates that one time period or era chronologically precedes another.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.