Triple
T32689083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shu forces |
E835805
|
entity |
| Predicate | founderOfCommand |
P196507
|
FINISHED |
| Object | Liu Bei |
—
|
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: Liu Bei | Statement: [Shu forces, founderOfCommand, Liu Bei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderOfCommand Context triple: [Shu forces, founderOfCommand, Liu Bei]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
foundingLeaderOf
Indicates that an entity is the primary founder who established and initially led another entity, such as an organization, movement, or institution.
-
C.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
D.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
E.
notableCommanderOf
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 1, 2026, 1:09 a.m.