Triple
T28896679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red (Gunstar Heroes) |
E732851
|
entity |
| Predicate | canCombineWeapons |
P17728
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Red (Gunstar Heroes), canCombineWeapons, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCombineWeapons Context triple: [Red (Gunstar Heroes), canCombineWeapons, true]
-
A.
wieldedFrom
Indicates that an entity uses or brandishes another entity as a weapon or tool originating from a particular source or location.
-
B.
supportsWeapon
chosen
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
C.
oftenEquippedWith
Indicates that one type of entity is frequently or typically outfitted, furnished, or supplied with another entity.
-
D.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
E.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa4ed148190bf84678627fdc598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:59 a.m.