Triple
T17335896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex |
E420931
|
entity |
| Predicate | order66InhibitorChip |
P127064
|
FINISHED |
| Object | removed |
—
|
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: removed | Statement: [Rex, order66InhibitorChip, removed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: order66InhibitorChip Context triple: [Rex, order66InhibitorChip, removed]
-
A.
madeTheKesselRunIn
Indicates that an entity completed the Kessel Run within a specified amount of time or distance.
-
B.
commandedByRebels
Indicates that the authority or control over an entity is exercised by rebel forces or insurgent groups.
-
C.
usesLightsaberOf
Indicates that one entity wields or makes use of the specific lightsaber that belongs to or is associated with another entity.
-
D.
starshipCommanded
Indicates that one entity serves as the commanding officer or authority in charge of operating and directing the other entity, which is a starship.
-
E.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
- F. None of above. chosen
Provenance (4 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a121aa081908a62fa59d3d28765 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.