Triple
T27811283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snap Wexley |
E702523
|
entity |
| Predicate | droidCompanionType |
P22642
|
FINISHED |
| Object | reprogrammed B1 battle droid |
—
|
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: reprogrammed B1 battle droid | Statement: [Snap Wexley, droidCompanionType, reprogrammed B1 battle droid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: droidCompanionType Context triple: [Snap Wexley, droidCompanionType, reprogrammed B1 battle droid]
-
A.
featuresCompanion
Indicates that one entity includes, presents, or is accompanied by another entity in a supporting or secondary role.
-
B.
companionChip
Indicates that one entity serves as a companion or auxiliary chip to another, typically functioning alongside it to provide additional or supporting capabilities.
-
C.
notableCompanionType
Indicates that one entity is a prominent or significant type of companion or associate in relation to another entity.
-
D.
supportsCompanion
Indicates that one entity provides assistance, encouragement, or backing to another entity in a companion or partner role.
-
E.
companionOf
chosen
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:42 p.m.