Triple
T29445006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massassi |
E746822
|
entity |
| Predicate | usedForcePowers |
P180245
|
FINISHED |
| Object | dark side rituals |
—
|
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: dark side rituals | Statement: [Massassi, usedForcePowers, dark side rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForcePowers Context triple: [Massassi, usedForcePowers, dark side rituals]
-
A.
usesForceUnder
Indicates that one entity applies physical power, coercion, or pressure to another entity while being positioned beneath or below it.
-
B.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
C.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
D.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
E.
usedForceUnder
Indicates that one entity applied or exerted force while positioned beneath or lower than another entity.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 28, 2026, 3:26 p.m.