Triple
T17445768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiande |
E424778
|
entity |
| Predicate | usedByDynastyType |
P126784
|
FINISHED |
| Object | Northern dynasty |
—
|
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: Northern dynasty | Statement: [Jiande, usedByDynastyType, Northern dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByDynastyType Context triple: [Jiande, usedByDynastyType, Northern dynasty]
-
A.
usedDuringDynasty
Indicates that something (such as an object, practice, or concept) was in use during the time period of a specific dynasty.
-
B.
dynasticUse
chosen
Indicates the use of something (such as a name, title, symbol, or resource) in a way that is tied to or characteristic of a particular dynasty or ruling family.
-
C.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
D.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
E.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.