Triple
T8552343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES |
E202472
|
entity |
| Predicate | developer |
P73
|
FINISHED |
| Object | SNK |
E202464
|
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: SNK | Statement: [AES, developer, SNK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SNK Context triple: [AES, developer, SNK]
-
A.
SNK
chosen
SNK is a Japanese video game company best known for its arcade and home console systems and fighting game franchises such as The King of Fighters, Samurai Shodown, and Metal Slug.
-
B.
Konami
Konami is a major Japanese entertainment company best known for developing and publishing popular video game franchises such as Metal Gear, Castlevania, and Silent Hill.
-
C.
Capcom
Capcom is a Japanese video game developer and publisher best known for creating major franchises such as Resident Evil, Street Fighter, and Monster Hunter.
-
D.
SNK hardware
SNK hardware refers to the family of arcade and home video game systems and related electronic platforms developed by the Japanese company SNK, best known for powering titles like those in the Neo Geo line.
-
E.
Jaleco
Jaleco was a Japanese video game company known for developing and publishing arcade and home console titles from the 1980s through the early 2000s.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe8882704819094b688d46169433a |
completed | March 31, 2026, 3:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd069faa481908db58399fe8f72f1 |
completed | April 3, 2026, 2:36 p.m. |
Created at: March 30, 2026, 6:19 p.m.