Triple
T28899462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Gear gang |
E732912
|
entity |
| Predicate | alsoAppearsAs |
P166014
|
FINISHED |
| Object | cameo references in Street Fighter titles |
—
|
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: cameo references in Street Fighter titles | Statement: [Mad Gear gang, alsoAppearsAs, cameo references in Street Fighter titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoAppearsAs Context triple: [Mad Gear gang, alsoAppearsAs, cameo references in Street Fighter titles]
-
A.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
B.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
appearsAgainst
Indicates that one entity is visually or publicly presented in opposition to, or in contrast with, another entity.
-
D.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
E.
appearsInFullNameOf
Indicates that one entity (typically a string or term) occurs as a contiguous part within the complete name of 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 8:01 a.m.