Triple
T38593596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fan of Blades |
E932509
|
entity |
| Predicate | comboWith |
P131235
|
FINISHED |
| Object | Swift Strike |
—
|
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: Swift Strike | Statement: [Fan of Blades, comboWith, Swift Strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comboWith Context triple: [Fan of Blades, comboWith, Swift Strike]
-
A.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
typicalCombinationWith
chosen
Indicates that one entity is commonly or characteristically used, found, or occurs together in combination with another entity.
-
D.
laterCombination
Indicates that one entity is a combination or composite that occurs after, or is formed subsequent to, another entity or state.
-
E.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.