Triple
T28283704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuanhe |
E713221
|
entity |
| Predicate | usedForReign |
P167069
|
FINISHED |
| Object | reign of Emperor Huizong of Song |
—
|
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: reign of Emperor Huizong of Song | Statement: [Xuanhe, usedForReign, reign of Emperor Huizong of Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForReign Context triple: [Xuanhe, usedForReign, reign of Emperor Huizong of Song]
-
A.
reusedDuringReignOf
Indicates that something previously existing was used again or repurposed during the period when a particular ruler or authority was in power.
-
B.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
C.
usedForRegnalYears
chosen
Indicates that something serves as the basis or reference system for counting and designating regnal years of a ruler.
-
D.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
E.
usedForMonarchOf
Indicates that something serves as a means, tool, or context specifically for exercising the role or authority of a monarch.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 11:24 p.m.