Triple
T23763846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reasoned Brightness |
E587322
|
entity |
| Predicate | usedAsEraNameBy |
P91459
|
FINISHED |
| Object | Daoguang Emperor |
—
|
NE NERFINISHED |
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: Daoguang Emperor | Statement: [Reasoned Brightness, usedAsEraNameBy, Daoguang Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsEraNameBy Context triple: [Reasoned Brightness, usedAsEraNameBy, Daoguang Emperor]
-
A.
usedEraName
chosen
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
B.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
C.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
D.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
E.
previousEraNameDerivedFrom
Indicates that the name of the current era is derived from, or based on, the name of a preceding era.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb40ee881908f3916cc6d05fc72 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.