Triple
T26405228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiankang |
E663812
|
entity |
| Predicate | eraOfUseAsName |
P2938
|
FINISHED |
| Object | 3rd to 6th centuries CE |
—
|
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: 3rd to 6th centuries CE | Statement: [Jiankang, eraOfUseAsName, 3rd to 6th centuries CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfUseAsName Context triple: [Jiankang, eraOfUseAsName, 3rd to 6th centuries CE]
-
A.
eraNameUsedInDocuments
Indicates that a particular era name is used as a temporal reference in the specified documents.
-
B.
eraNameType
Indicates the type or classification of a named historical or chronological era associated with an entity.
-
C.
usedEraName
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
D.
eraName
chosen
Indicates the named historical or chronological era associated with an entity or time period.
-
E.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:34 p.m.