Triple
T26369222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liu Song |
E660724
|
entity |
| Predicate | successorDynastyInSouthernChina |
P1551
|
FINISHED |
| Object | Southern Qi |
—
|
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: Southern Qi | Statement: [Liu Song, successorDynastyInSouthernChina, Southern Qi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyInSouthernChina Context triple: [Liu Song, successorDynastyInSouthernChina, Southern Qi]
-
A.
successorInChina
Indicates that one entity directly follows or replaces another in a position, role, or sequence within the context of China.
-
B.
successorDynasty
chosen
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
C.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
D.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
E.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 26, 2026, 10:57 p.m.