Triple
T8008214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kylo Ren |
E186417
|
entity |
| Predicate | usesForce |
P62418
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kylo Ren, usesForce, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForce Context triple: [Kylo Ren, usesForce, yes]
-
A.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
B.
forcesAction
Indicates that one entity compels or coerces another entity to perform a specific action or behavior.
-
C.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that entity.
-
D.
forces
Indicates that one entity compels or obliges another entity to perform an action or be in a certain state, typically against the latter’s will or without full freedom of choice.
-
E.
invokesPower
chosen
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d6e1c9081909018bcebb18906f6 |
completed | March 31, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:19 p.m.