Triple
T27934667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Squadron |
E708071
|
entity |
| Predicate | objectiveInBattleOfYavin |
P42909
|
FINISHED |
| Object | destroy the Death Star |
—
|
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: destroy the Death Star | Statement: [Red Squadron, objectiveInBattleOfYavin, destroy the Death Star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveInBattleOfYavin Context triple: [Red Squadron, objectiveInBattleOfYavin, destroy the Death Star]
-
A.
goalOfRebelSide
Indicates that the specified goal is pursued or held by the rebel side in a conflict or opposition scenario.
-
B.
madeTheKesselRunIn
Indicates that an entity completed the Kessel Run within a specified amount of time or distance.
-
C.
militaryCampaignObjective
Indicates that a military campaign is conducted with the specific aim or goal of achieving a particular strategic, operational, or tactical objective.
-
D.
intendedMission
chosen
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
usesStarfighter
Indicates that one entity operates or employs a starfighter as its vehicle, tool, or means of transportation or combat.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:04 p.m.