Triple
T28076094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Campaign against the Nanman |
E709545
|
entity |
| Predicate | commandedByState |
P1407
|
FINISHED |
| Object | Shu Han |
—
|
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: Shu Han | Statement: [Southern Campaign against the Nanman, commandedByState, Shu Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedByState Context triple: [Southern Campaign against the Nanman, commandedByState, Shu Han]
-
A.
commandedBy
chosen
Indicates that one entity holds authoritative control or issues orders over another entity.
-
B.
commandingState
Indicates that one entity holds authoritative control or directive power over another, typically giving orders or instructions that the other is expected to follow.
-
C.
commandedByFrom
Indicates that an entity is under the authority or control of another entity originating from a specified source or location.
-
D.
commandedBySide
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 8:49 p.m.