Triple
T37880808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 建武 |
E944859
|
entity |
| Predicate | hasEraNameVariant |
P66486
|
FINISHED |
| Object | 建武元年 |
—
|
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: 建武元年 | Statement: [建武, hasEraNameVariant, 建武元年]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraNameVariant Context triple: [建武, hasEraNameVariant, 建武元年]
-
A.
usedEraName
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
B.
subjectHasEra
Indicates that a subject is associated with, defined by, or belongs to a particular historical or temporal era.
-
C.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
D.
hasHistoricNameVariant
chosen
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
E.
precedesEraName
Indicates that one era occurs entirely before another era in chronological order.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.