Triple
T26943598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander Cody |
E678579
|
entity |
| Predicate | order66Participation |
P167763
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Commander Cody, order66Participation, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: order66Participation Context triple: [Commander Cody, order66Participation, Yes]
-
A.
orderedToParticipateIn
Indicates that one entity has been formally directed or commanded by another entity to take part in a specific activity, event, or operation.
-
B.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
-
C.
hasRitualParticipants
Indicates that a ritual involves specific participants who take part in its performance or observance.
-
D.
participantCustom
Indicates that an entity participates in an event, activity, or process in a role or manner that is defined in a customized or non-standard way.
-
E.
requiresParticipationOf
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 6:20 a.m.