Triple
T29188566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Force |
E739933
|
entity |
| Predicate | canBeSensedBy |
P93007
|
FINISHED |
| Object | Force-sensitive beings |
—
|
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: Force-sensitive beings | Statement: [the Force, canBeSensedBy, Force-sensitive beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSensedBy Context triple: [the Force, canBeSensedBy, Force-sensitive beings]
-
A.
hasSensor
Indicates that one entity is equipped with, contains, or uses a particular sensor.
-
B.
sensingAction
Indicates an action in which an entity perceives, detects, or measures some property, signal, or condition of another entity or its environment.
-
C.
sensorTypesInvolved
Indicates the types of sensors that participate in or are utilized within a given event, process, or system.
-
D.
requiresExternalSensors
Indicates that performing this action or maintaining this relationship depends on input or data from sensors that are external to the entity itself.
-
E.
hasSensation
chosen
Indicates that an entity experiences or is subject to a particular sensory or perceptual feeling.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 12:01 p.m.