Triple
T36068736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenji |
E1043306
|
entity |
| Predicate | startEraJapaneseDate |
P131207
|
FINISHED |
| Object | Daiji 4, 3rd month, 3rd day |
—
|
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: Daiji 4, 3rd month, 3rd day | Statement: [Tenji, startEraJapaneseDate, Daiji 4, 3rd month, 3rd day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startEraJapaneseDate Context triple: [Tenji, startEraJapaneseDate, Daiji 4, 3rd month, 3rd day]
-
A.
startEraInJapaneseCalendar
chosen
Indicates the point in time when a specific era begins within the Japanese calendar system.
-
B.
startEraYearGregorian
Indicates the Gregorian calendar year in which a particular era or period begins.
-
C.
startEraDay
Indicates the specific calendar day on which a particular era or period begins.
-
D.
eraStartHeiseiYear
Indicates the calendar year in which the Heisei era begins for a given context or system of dating.
-
E.
startOfEdoPeriod
Indicates that something marks the beginning or initial phase of the Edo period in Japanese history.
- 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_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: May 3, 2026, 4:08 p.m.