Triple
T14461394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cad Bane |
E358590
|
entity |
| Predicate | statusInTheBookOfBobaFett |
P114739
|
FINISHED |
| Object | killed by Boba Fett (in canon) |
—
|
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: killed by Boba Fett (in canon) | Statement: [Cad Bane, statusInTheBookOfBobaFett, killed by Boba Fett (in canon)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInTheBookOfBobaFett Context triple: [Cad Bane, statusInTheBookOfBobaFett, killed by Boba Fett (in canon)]
-
A.
JediRank
Indicates the formal rank or level of status a Jedi holds within the Jedi Order hierarchy.
-
B.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
C.
roleDuringCloneWars
Indicates the specific function, position, or duties an entity held during the time period of the Clone Wars.
-
D.
C-32BRole
Indicates that an entity holds or is assigned a specific role or function within the context labeled C-32B.
-
E.
madeTheKesselRunIn
Indicates that an entity completed the Kessel Run within a specified amount of time or distance.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:19 a.m.