Triple
T17630897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Former Qin |
E429971
|
entity |
| Predicate | causeOfFragmentation |
P694
|
FINISHED |
| Object | internal rebellions |
—
|
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: internal rebellions | Statement: [Former Qin, causeOfFragmentation, internal rebellions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfFragmentation Context triple: [Former Qin, causeOfFragmentation, internal rebellions]
-
A.
fragmentationLevel
Indicates the degree to which something is broken into smaller, separate parts or segments.
-
B.
fragility
Indicates that an entity is easily damaged, broken, or adversely affected when subjected to stress, force, or change.
-
C.
successorStateFragmentation
Indicates that a successor state experiences division or breakup into multiple smaller political or administrative units.
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dc192dc8190854f1fe5d5ed696a |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.