Triple
T36112548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Gubeikou (Ming–Mongol conflicts) |
E1044536
|
entity |
| Predicate | aimOfMongols |
P185033
|
FINISHED |
| Object | break Ming frontier defenses |
—
|
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: break Ming frontier defenses | Statement: [Battle of Gubeikou (Ming–Mongol conflicts), aimOfMongols, break Ming frontier defenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfMongols Context triple: [Battle of Gubeikou (Ming–Mongol conflicts), aimOfMongols, break Ming frontier defenses]
-
A.
impactOnMongols
Indicates the effect or influence that something has on the Mongols.
-
B.
viewOnMongols
Indicates the stance, opinion, or perspective that one entity holds regarding the Mongols.
-
C.
aimOfMamluks
Indicates that the specified goal, objective, or purpose is attributed to or pursued by the Mamluks.
-
D.
aimOfByzantines
Indicates the goal or objective pursued by the Byzantines in a given context.
-
E.
pre-MongolRuler
Indicates that one entity served as a ruler before the period of Mongol domination or rule over the relevant region.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:08 p.m.