Triple
T28096110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenfeng |
E710095
|
entity |
| Predicate | usedInDynasticContext |
P111642
|
FINISHED |
| Object | Eastern Wu regime |
—
|
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: Eastern Wu regime | Statement: [Shenfeng, usedInDynasticContext, Eastern Wu regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDynasticContext Context triple: [Shenfeng, usedInDynasticContext, Eastern Wu regime]
-
A.
dynasticContext
Indicates the historical or political circumstances defined by a particular ruling dynasty under which the related entities or events are situated.
-
B.
dynasticUse
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.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
D.
belongsToDynasticHistory
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
-
E.
usedDuringDynasty
chosen
Indicates that something (such as an object, practice, or concept) was in use during the time period of a specific 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 9:01 p.m.