Triple
T26618484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaapad |
E668129
|
entity |
| Predicate | notablyUsedAgainst |
P13821
|
FINISHED |
| Object | Darth Sidious |
—
|
NE NERFINISHED |
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: Darth Sidious | Statement: [Vaapad, notablyUsedAgainst, Darth Sidious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyUsedAgainst Context triple: [Vaapad, notablyUsedAgainst, Darth Sidious]
-
A.
usedAgainst
chosen
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
B.
effectivenessAgainst
Indicates how well one entity performs in countering, influencing, or mitigating the impact of another entity.
-
C.
skillUsedFor
Indicates that a particular skill is employed or applied to perform, achieve, or facilitate a specific task, goal, or function.
-
D.
notablyUsedWith
Indicates that one entity is commonly or prominently used together with another entity, in a way that is especially characteristic or noteworthy.
-
E.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 27, 2026, 2:19 a.m.