Triple
T28284034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New History of the Five Dynasties |
E713230
|
entity |
| Predicate | dynastyOfComposition |
P165434
|
FINISHED |
| Object | Song dynasty |
—
|
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: Song dynasty | Statement: [New History of the Five Dynasties, dynastyOfComposition, Song dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyOfComposition Context triple: [New History of the Five Dynasties, dynastyOfComposition, Song dynasty]
-
A.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
B.
creatorDynasty
Indicates the historical dynasty or ruling period during which the creator of an entity lived or was active.
-
C.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
D.
historicalComposition
Indicates that one entity was historically part of, or contributed to the makeup or structure of, another entity during a past period.
-
E.
dynastyDescribedAs
Indicates that a dynasty is characterized or labeled using a particular description, epithet, or qualitative phrase.
- F. None of above. chosen
Provenance (4 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_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 11:25 p.m.