Triple
T3888943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pax Mongolica |
E88009
|
entity |
| Predicate | hasEndCause |
P708
|
FINISHED |
| Object | fragmentation of Mongol Empire |
—
|
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: fragmentation of Mongol Empire | Statement: [Pax Mongolica, hasEndCause, fragmentation of Mongol Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndCause Context triple: [Pax Mongolica, hasEndCause, fragmentation of Mongol Empire]
-
A.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
B.
hasCause
chosen
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
D.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
-
E.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecad4bf081909ae45a69d22468fa |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.