Triple
T36505481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark troopers |
E899447
|
entity |
| Predicate | notableDefeatBy |
P51330
|
FINISHED |
| Object | Luke Skywalker |
E173035
|
NE 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: Luke Skywalker | Statement: [Dark troopers, notableDefeatBy, Luke Skywalker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDefeatBy Context triple: [Dark troopers, notableDefeatBy, Luke Skywalker]
-
A.
notableDefeatContext
Indicates a contextual relationship in which a notable or significant defeat of an entity occurs, specifying the circumstances or setting of that defeat.
-
B.
significantDefeat
chosen
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
C.
dateOfMajorDefeat
Indicates the specific date on which an entity experienced a significant or decisive defeat.
-
D.
eventuallyDefeatedBy
Indicates that one entity is ultimately overcome, beaten, or conquered by another, possibly after some duration or sequence of events.
-
E.
locationOfMajorDefeat
Indicates the place where a significant or decisive defeat of a party occurred.
- F. None of above.
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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbd340848190aad6d59bf1ed8479 |
completed | June 23, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.