Triple
T30260606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Gillard |
E769479
|
entity |
| Predicate | designedFightFor |
P193358
|
FINISHED |
| Object | Duel of the Fates lightsaber battle |
—
|
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: Duel of the Fates lightsaber battle | Statement: [Nick Gillard, designedFightFor, Duel of the Fates lightsaber battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedFightFor Context triple: [Nick Gillard, designedFightFor, Duel of the Fates lightsaber battle]
-
A.
designedToDefeat
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
B.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
C.
fightType
Indicates the specific category or style of fight associated with an event or interaction between entities.
-
D.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
E.
fought
Indicates that one entity engaged in physical or armed conflict or combat against 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: April 29, 2026, 7:41 p.m.