Triple
T25277840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chirrut Îmwe |
E633747
|
entity |
| Predicate | sensitivityToForce |
P77486
|
FINISHED |
| Object | spiritually attuned to the Force |
—
|
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: spiritually attuned to the Force | Statement: [Chirrut Îmwe, sensitivityToForce, spiritually attuned to the Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sensitivityToForce Context triple: [Chirrut Îmwe, sensitivityToForce, spiritually attuned to the Force]
-
A.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
B.
forceSensitive
chosen
Indicates that an entity has an innate connection to and ability to perceive or use a mystical or supernatural energy or power.
-
C.
isPressureSensitive
Indicates that an entity responds differently based on the amount or intensity of physical pressure applied to it.
-
D.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
E.
axisForce
Indicates a force applied along a specific axis or direction between entities.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba8e99081908b3fd911e8634dcc |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:18 p.m.