Triple
T10470913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Phasma |
E246917
|
entity |
| Predicate | forcedTo |
P4672
|
FINISHED |
| Object | lower Starkiller Base shields |
—
|
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: lower Starkiller Base shields | Statement: [Captain Phasma, forcedTo, lower Starkiller Base shields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedTo Context triple: [Captain Phasma, forcedTo, lower Starkiller Base shields]
-
A.
forcedBy
chosen
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
B.
forcedToReturnTo
Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
-
C.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
D.
forceSensitive
Indicates that an entity has an innate connection to and ability to perceive or use a mystical or supernatural energy or power.
-
E.
enteredIntoForce
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509305fec81908b1acd91ae1f875d |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.