Triple
T28288293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guang |
E713347
|
entity |
| Predicate | associatedDynastyThroughBearer |
P203106
|
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: [Guang, associatedDynastyThroughBearer, Song dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynastyThroughBearer Context triple: [Guang, associatedDynastyThroughBearer, Song dynasty]
-
A.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
C.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
-
D.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
E.
belongsToDynasticHistory
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
- 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_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_6a0120ef753c81909894e53013b33f03 |
completed | May 11, 2026, 12:21 a.m. |
Created at: April 27, 2026, 11:27 p.m.