Triple
T28898955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darius |
E732901
|
entity |
| Predicate | originalArcadeCabinetType |
P21145
|
FINISHED |
| Object | triple-screen cabinet |
—
|
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: triple-screen cabinet | Statement: [Darius, originalArcadeCabinetType, triple-screen cabinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalArcadeCabinetType Context triple: [Darius, originalArcadeCabinetType, triple-screen cabinet]
-
A.
manufacturerOfArcadeCabinet
Indicates that one entity is the company or maker responsible for producing a particular arcade cabinet.
-
B.
arcadeSystemVariant
Indicates that one arcade system is a specific version, configuration, or variant derived from another arcade system.
-
C.
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).
-
D.
cabinetType
chosen
Indicates the specific kind or category of cabinet associated with an entity.
-
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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 28, 2026, 8:01 a.m.