Triple
T15286580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuanzong |
E365415
|
entity |
| Predicate | centuryOfBearerReign |
P112293
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Xuanzong, centuryOfBearerReign, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfBearerReign Context triple: [Xuanzong, centuryOfBearerReign, 15th century]
-
A.
centuryOfReign
chosen
Indicates the century during which a given entity’s reign or rule took place.
-
B.
yearOfReign
Indicates the specific year or span of years during which a ruler or authority held official power or reigned.
-
C.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
D.
reachedRoyalStatusInCentury
Indicates that an entity attained royal status or became recognized as royalty during a specified century.
-
E.
ended reign start year
Indicates the calendar year in which a ruler’s period of reign came to an end.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e551bb0819094db097285443740 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.