Triple
T32064621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q*bert |
E818839
|
entity |
| Predicate | arcadeHardware |
P165506
|
FINISHED |
| Object | Gottlieb System 1 |
—
|
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: Gottlieb System 1 | Statement: [Q*bert, arcadeHardware, Gottlieb System 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arcadeHardware Context triple: [Q*bert, arcadeHardware, Gottlieb System 1]
-
A.
arcadeHardwareDeveloper
chosen
Indicates that an entity is responsible for designing or developing hardware used in arcade game systems.
-
B.
arcadeStandard
Indicates that something conforms to, or is defined as, the standard or typical form used in arcade contexts (such as games, machines, or configurations).
-
C.
arcadeSystemVariant
Indicates that one arcade system is a specific version, configuration, or variant derived from another arcade system.
-
D.
notableArcadeGame
Indicates that the subject is an arcade game that is particularly famous, influential, or otherwise noteworthy.
-
E.
hasArcades
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f85ea881908ce0bbddd9426e73 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:22 a.m.