Triple
T28612944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sega arcade systems |
E724210
|
entity |
| Predicate | notableGamePowered |
P84766
|
FINISHED |
| Object | Virtua Fighter |
—
|
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: Virtua Fighter | Statement: [Sega arcade systems, notableGamePowered, Virtua Fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGamePowered Context triple: [Sega arcade systems, notableGamePowered, Virtua Fighter]
-
A.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
B.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
C.
notableGameUsingService
chosen
Indicates that a particular game is prominently known for using or being built upon a specific service or platform.
-
D.
notableBuiltInGame
Indicates that an entity is a well-known or significant game that is pre-installed or comes bundled by default within another product or platform.
-
E.
notableGameWorld
Indicates that a game’s world or setting is particularly significant, distinguished, or noteworthy in some meaningful way.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: April 28, 2026, 4:30 a.m.