Triple
T29297100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Sith Wars |
E742861
|
entity |
| Predicate | factionCharacteristic |
P166816
|
FINISHED |
| Object | Sith infighting and fragmentation |
—
|
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: Sith infighting and fragmentation | Statement: [New Sith Wars, factionCharacteristic, Sith infighting and fragmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionCharacteristic Context triple: [New Sith Wars, factionCharacteristic, Sith infighting and fragmentation]
-
A.
battleCharacteristic
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
-
B.
factionType
Indicates the classification or category of a faction within a broader system or context.
-
C.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
D.
factionSymbol
Indicates the specific faction with which an entity is associated or aligned.
-
E.
factionRole
Indicates the specific role, function, or position an entity holds within a particular faction or group.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654459b481908684b3efa19d5bd5 |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:07 p.m.