Triple
T29111569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongning |
E736920
|
entity |
| Predicate | chronologyRole |
P180238
|
FINISHED |
| Object | designates specific reign period |
—
|
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: designates specific reign period | Statement: [Yongning, chronologyRole, designates specific reign period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyRole Context triple: [Yongning, chronologyRole, designates specific reign period]
-
A.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
C.
chronologyIn
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
-
D.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
E.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
- F. None of above. chosen
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 28, 2026, 11:19 a.m.