Triple
T28076126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Northern Expedition |
E709546
|
entity |
| Predicate | outcomeForShuHan |
P59870
|
FINISHED |
| Object | strategic failure |
—
|
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: strategic failure | Statement: [First Northern Expedition, outcomeForShuHan, strategic failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForShuHan Context triple: [First Northern Expedition, outcomeForShuHan, strategic failure]
-
A.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
ShuForces
Indicates a relationship where forces or military units are associated with, belong to, or act on behalf of the Shu faction or state.
-
C.
outcomeForJapan
Indicates the result, consequence, or impact that an event, action, or situation has specifically for Japan.
-
D.
resultOfSurrender
Indicates that something exists or occurs as a consequence or outcome of a surrender event or act of capitulation.
-
E.
outcomeForThasos
Indicates the result, consequence, or effect that an event, action, or situation has specifically for Thasos.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 8:49 p.m.