Triple
T28288249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song Emperor Bing |
E713346
|
entity |
| Predicate | dynasticTempleName |
P91780
|
FINISHED |
| Object | Bing |
—
|
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: Bing | Statement: [Song Emperor Bing, dynasticTempleName, Bing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticTempleName Context triple: [Song Emperor Bing, dynasticTempleName, Bing]
-
A.
dynasticNameDerivedFrom
Indicates that a dynastic name is derived from, or based on, another name, title, or source.
-
B.
hasEmperorTempleName
chosen
Indicates that an emperor is associated with a specific posthumous temple name used in imperial ancestral worship.
-
C.
epithetOfDynasty
Indicates that a particular epithet (honorific or descriptive title) is associated with and used to refer to a specific dynasty.
-
D.
reignInDynasty
Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
-
E.
eraNameUsedDuringReign
Indicates that a particular era name was officially used throughout the duration of a 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 11:27 p.m.