Triple
T28096050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Deng |
E710093
|
entity |
| Predicate | hadRetinueOf |
P4079
|
FINISHED |
| Object | virtuous officials |
—
|
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: virtuous officials | Statement: [Sun Deng, hadRetinueOf, virtuous officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRetinueOf Context triple: [Sun Deng, hadRetinueOf, virtuous officials]
-
A.
hadSecondInCommand
Indicates that one entity had another entity serving as its second-in-command or primary subordinate leader.
-
B.
hasServant
chosen
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
C.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
-
D.
hasNumberOfCompanions
Indicates the quantity of companions or associates that an entity has.
-
E.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
- 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_69f6408d714481908423227f6a8b655f |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:01 p.m.