Triple
T17353124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force lightning |
E421862
|
entity |
| Predicate | canBeDeflectedBy |
P119086
|
FINISHED |
| Object | lightsaber blade |
—
|
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: lightsaber blade | Statement: [Force lightning, canBeDeflectedBy, lightsaber blade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDeflectedBy Context triple: [Force lightning, canBeDeflectedBy, lightsaber blade]
-
A.
canBeDodgedBy
Indicates that an action, effect, or attack is avoidable by a particular entity through dodging.
-
B.
canRicochetOff
chosen
Indicates that one object is capable of bouncing or deflecting off the surface of another object rather than stopping or passing through.
-
C.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
D.
deflectionType
Indicates the specific manner or category of how something is diverted, redirected, or caused to change its original course or direction.
-
E.
cannotBeDamagedBy
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.