Triple
T28571539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi family |
E723125
|
entity |
| Predicate | imperialPeriodStart |
P28474
|
FINISHED |
| Object | 1897 |
—
|
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: 1897 | Statement: [Yi family, imperialPeriodStart, 1897]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialPeriodStart Context triple: [Yi family, imperialPeriodStart, 1897]
-
A.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
-
B.
historicalMigrationPeriodStart
Indicates the point in time when a particular historical migration period begins.
-
C.
timePeriodOfImperialRole
chosen
Indicates the span of time during which an entity held or exercised an imperial role or authority.
-
D.
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.
-
E.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650930d088190982ac09775d5b177 |
completed | May 2, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:10 a.m.