Triple
T27774461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hexi Corridor |
E699145
|
entity |
| Predicate | effectOnXiongnu |
P173229
|
FINISHED |
| Object | loss of strategic positions in Hexi Corridor |
—
|
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: loss of strategic positions in Hexi Corridor | Statement: [Battle of Hexi Corridor, effectOnXiongnu, loss of strategic positions in Hexi Corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnXiongnu Context triple: [Battle of Hexi Corridor, effectOnXiongnu, loss of strategic positions in Hexi Corridor]
-
A.
effectOnCossacks
Indicates the impact or consequences that something has on Cossacks as a group.
-
B.
effectOnPolity
Indicates the impact or consequence that one entity, event, or action has on a political body or governing organization.
-
C.
effectOnInvasion
Indicates the influence or impact that one factor has on the occurrence, success, or intensity of an invasion.
-
D.
effectOnRace
Indicates that one entity has an influence or impact on the outcome, dynamics, or characteristics of a race.
-
E.
impactOnPechenegs
Indicates the effect or influence that one entity or event has on the Pechenegs.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 5:04 p.m.