Triple
T35647622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D'deridex-class warbird |
E1030051
|
entity |
| Predicate | typicalOpponentClass |
P116426
|
FINISHED |
| Object | Galaxy-class starship |
—
|
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: Galaxy-class starship | Statement: [D'deridex-class warbird, typicalOpponentClass, Galaxy-class starship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOpponentClass Context triple: [D'deridex-class warbird, typicalOpponentClass, Galaxy-class starship]
-
A.
featuresOpponentType
Indicates that an entity involves, includes, or is associated with an opponent of a specified type within a competitive or adversarial context.
-
B.
traditionalOpponents
Indicates that two entities customarily or historically compete or conflict with each other as recognized rivals or adversaries.
-
C.
enemyTypeOpposed
Indicates that one type of enemy is defined as being in opposition or conflict with another enemy type.
-
D.
associatedOpponent
chosen
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
regularOpponent
Indicates that two entities frequently compete against each other as recurring opponents in some contest or competitive context.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.