Triple
T30590743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changli Xiansheng |
E778645
|
entity |
| Predicate | bearerEraName |
P91459
|
FINISHED |
| Object | Zhenyuan era |
—
|
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: Zhenyuan era | Statement: [Changli Xiansheng, bearerEraName, Zhenyuan era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerEraName Context triple: [Changli Xiansheng, bearerEraName, Zhenyuan era]
-
A.
usedEraName
chosen
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
B.
bearerNotableEra
Indicates that a bearer (such as a title, role, or office) is notably associated with a particular historical era or time period.
-
C.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
D.
subjectHasEra
Indicates that a subject is associated with, defined by, or belongs to a particular historical or temporal era.
-
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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 8:24 p.m.