Triple
T10322006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Injuids |
E242157
|
entity |
| Predicate | collapseReason |
P77396
|
FINISHED |
| Object | conquest by Muzaffarids |
—
|
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: conquest by Muzaffarids | Statement: [Injuids, collapseReason, conquest by Muzaffarids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapseReason Context triple: [Injuids, collapseReason, conquest by Muzaffarids]
-
A.
collapsedDueTo
chosen
Indicates that one entity fell down, caved in, or structurally failed as a result of another specified cause or factor.
-
B.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
C.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
D.
collapseEvent
Indicates an event in which a structure, system, or entity suddenly falls apart, fails, or loses its integrity.
-
E.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:50 a.m.