Triple
T29321900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obi-Wan Kenobi |
E743536
|
entity |
| Predicate | order66Survivor |
P173258
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Obi-Wan Kenobi, order66Survivor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: order66Survivor Context triple: [Obi-Wan Kenobi, order66Survivor, true]
-
A.
order66InhibitorChip
Indicates that an entity possesses or is affected by the control chip designed to enforce or trigger compliance with Order 66.
-
B.
order66Participation
Indicates participation in carrying out Order 66, i.e., being involved in the execution of that specific directive or operation.
-
C.
outcomeForSith
Indicates the resulting state, consequence, or effect that an event, action, or situation has specifically for a Sith.
-
D.
commandedByRebels
Indicates that the authority or control over an entity is exercised by rebel forces or insurgent groups.
-
E.
escortCommander
Indicates that one entity serves as the commanding officer responsible for leading or overseeing an escort force or mission involving another entity.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 28, 2026, 1:23 p.m.