Triple
T26943475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clone Force 99 |
E678576
|
entity |
| Predicate | laterOpponents |
P84463
|
FINISHED |
| Object | Galactic Empire |
—
|
NE NERFINISHED |
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: Galactic Empire | Statement: [Clone Force 99, laterOpponents, Galactic Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterOpponents Context triple: [Clone Force 99, laterOpponents, Galactic Empire]
-
A.
laterOpponent
chosen
Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
-
B.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
C.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
D.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
-
E.
intendedOpponents
Indicates that one entity is the target or adversary that another entity is meant or designed to oppose or confront.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 6:20 a.m.