Triple
T32824259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiaolu |
E839512
|
entity |
| Predicate | usedInRegnalChronology |
P167069
|
FINISHED |
| Object | Tang dynasty chronology |
—
|
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: Tang dynasty chronology | Statement: [Tiaolu, usedInRegnalChronology, Tang dynasty chronology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRegnalChronology Context triple: [Tiaolu, usedInRegnalChronology, Tang dynasty chronology]
-
A.
usedForRegnalYears
chosen
Indicates that something serves as the basis or reference system for counting and designating regnal years of a ruler.
-
B.
usedRegnalNumber
Indicates that an entity (such as a ruler or pope) bore or was designated by a specific regnal number as part of their official title.
-
C.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
-
D.
usedByRegnalName
Indicates that a particular regnal name is borne or employed by a specific ruler or monarch.
-
E.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 1, 2026, 1:15 a.m.