Triple
T28065770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wang Anshi |
E709244
|
entity |
| Predicate | reignOfService |
P87031
|
FINISHED |
| Object | Emperor Shenzong of Song |
—
|
NE NERFINISHED |
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: Emperor Shenzong of Song | Statement: [Wang Anshi, reignOfService, Emperor Shenzong of Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignOfService Context triple: [Wang Anshi, reignOfService, Emperor Shenzong of Song]
-
A.
reignCertainty
Indicates how certain or uncertain it is that a particular reign or period of rule actually occurred or is correctly assigned.
-
B.
reignSupportedBy
Indicates that a ruler’s period of rule is backed, upheld, or sustained by a particular person, group, or power.
-
C.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
D.
reignStatus
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
-
E.
underTheReignOf
chosen
Indicates that one entity existed or operated during the period when another entity (typically a ruler or authority) held power or governance.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 8:42 p.m.