Triple
T33941372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunji |
E870173
|
entity |
| Predicate | startEraYearGregorian |
P201441
|
FINISHED |
| Object | 1185-08-14 |
—
|
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: 1185-08-14 | Statement: [Bunji, startEraYearGregorian, 1185-08-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startEraYearGregorian Context triple: [Bunji, startEraYearGregorian, 1185-08-14]
-
A.
startEraDay
Indicates the specific calendar day on which a particular era or period begins.
-
B.
startEraInJapaneseCalendar
Indicates the point in time when a specific era begins within the Japanese calendar system.
-
C.
startEraMonth
Indicates the calendar month in which a particular era or period begins.
-
D.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
-
E.
endEraInGregorianCalendar
Indicates that a particular era or historical period concludes on a specified date in the Gregorian calendar.
- F. None of above. chosen
Provenance (4 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fff59875cc8190864864e951951679 |
completed | May 10, 2026, 3:03 a.m. |
Created at: May 1, 2026, 1:49 a.m.