Triple
T28801619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Diaoyu Castle |
E727250
|
entity |
| Predicate | impactOnMongols |
P175244
|
FINISHED |
| Object | halted Mongol advance in the region |
—
|
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: halted Mongol advance in the region | Statement: [Battle of Diaoyu Castle, impactOnMongols, halted Mongol advance in the region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnMongols Context triple: [Battle of Diaoyu Castle, impactOnMongols, halted Mongol advance in the region]
-
A.
viewOnMongols
Indicates the stance, opinion, or perspective that one entity holds regarding the Mongols.
-
B.
impactOnPechenegs
Indicates the effect or influence that one entity or event has on the Pechenegs.
-
C.
impactOnConstantinople
Indicates a relationship where one entity has an effect, influence, or consequence specifically on the city of Constantinople.
-
D.
effectOnMughals
Indicates the impact or influence that something has on the Mughals, such as how an event, action, or condition affects their state, power, or circumstances.
-
E.
roleAtMongolCourt
Indicates a person's specific position, function, or status within the Mongol imperial court.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 6:27 a.m.