Triple
T32489720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianxing (continuation from Sun Quan) |
E830348
|
entity |
| Predicate | reusedDuringReignOf |
P174500
|
FINISHED |
| Object | Sun Liang |
—
|
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: Sun Liang | Statement: [Jianxing (continuation from Sun Quan), reusedDuringReignOf, Sun Liang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reusedDuringReignOf Context triple: [Jianxing (continuation from Sun Quan), reusedDuringReignOf, Sun Liang]
-
A.
modifiedDuringReignOf
Indicates that an entity was altered, updated, or changed while a particular ruler or authority was in power.
-
B.
builtDuringReignOf
Indicates that something was constructed while a particular ruler or authority was in power.
-
C.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
-
D.
renamedDuringReignOf
Indicates that an entity received a new name while a specified ruler or authority was in power.
-
E.
lostDuringReignOf
Indicates that something ceased to exist, was destroyed, or disappeared during the period when a particular ruler or authority was in power.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3faab78819095c5bfa180e15186 |
completed | May 3, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:59 a.m.