Triple
T26943599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander Cody |
E678579
|
entity |
| Predicate | turnedOn |
P161353
|
FINISHED |
| Object | Obi-Wan Kenobi during Order 66 |
—
|
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: Obi-Wan Kenobi during Order 66 | Statement: [Commander Cody, turnedOn, Obi-Wan Kenobi during Order 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnedOn Context triple: [Commander Cody, turnedOn, Obi-Wan Kenobi during Order 66]
-
A.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
B.
turnedPro
Indicates that an individual transitioned from amateur status to professional status in a particular field or activity.
-
C.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
D.
airedOn
Indicates that a broadcasted program or episode was shown on a specific channel, platform, or medium.
-
E.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62082e298819088389b3bb529fb60 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:20 a.m.