Triple
T36068799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten’yō |
E1043308
|
entity |
| Predicate | predecessorEraStartYear |
P195841
|
FINISHED |
| Object | 1126 |
—
|
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: 1126 | Statement: [Ten’yō, predecessorEraStartYear, 1126]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEraStartYear Context triple: [Ten’yō, predecessorEraStartYear, 1126]
-
A.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
B.
precedesEraName
Indicates that one era occurs entirely before another era in chronological order.
-
C.
originYearOfPredecessor
Indicates the calendar year in which the predecessor entity first originated or was established.
-
D.
predecessorRulerEraSystem
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
-
E.
eraStartYearBC
Indicates the year (counting backward from year 1) in which a particular era or period begins, expressed in the BC (Before Christ/BCE) dating system.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.