Triple
T4407504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kertanegara |
E93769
|
entity |
| Predicate | mutilated |
P18372
|
FINISHED |
| Object | Yuan envoys sent by Kublai Khan |
—
|
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: Yuan envoys sent by Kublai Khan | Statement: [Kertanegara, mutilated, Yuan envoys sent by Kublai Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mutilated Context triple: [Kertanegara, mutilated, Yuan envoys sent by Kublai Khan]
-
A.
corrupts
Indicates that one entity causes another entity, system, or process to become morally, functionally, or structurally degraded or impaired.
-
B.
undermined
Indicates that one entity has weakened, subverted, or reduced the effectiveness, authority, or stability of another entity or its position.
-
C.
broken
chosen
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
D.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
-
E.
stricken
Indicates that an entity has been severely affected, harmed, or afflicted by something (such as illness, disaster, or misfortune).
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b3548b1ca08190b3136867c7098d86 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.