Triple
T29297093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Sith Wars |
E742861
|
entity |
| Predicate | outcomeForJedi |
P170424
|
FINISHED |
| Object | reduction of Jedi military role |
—
|
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: reduction of Jedi military role | Statement: [New Sith Wars, outcomeForJedi, reduction of Jedi military role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForJedi Context triple: [New Sith Wars, outcomeForJedi, reduction of Jedi military role]
-
A.
outcomeForSith
Indicates the resulting state, consequence, or effect that an event, action, or situation has specifically for a Sith.
-
B.
fellOneWinShortOf
Indicates that an entity narrowly missed achieving a win, finishing just one victory short of a desired or required total.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
JediRank
Indicates the formal rank or level of status a Jedi holds within the Jedi Order hierarchy.
-
E.
distinctionFromSith
Indicates that one entity is explicitly characterized as being different or separate from Sith.
- 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_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 28, 2026, 1:07 p.m.