Triple
T31871917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo |
E813625
|
entity |
| Predicate | handheldVariant |
P66849
|
FINISHED |
| Object | Neo Geo Pocket |
—
|
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: Neo Geo Pocket | Statement: [Neo Geo, handheldVariant, Neo Geo Pocket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handheldVariant Context triple: [Neo Geo, handheldVariant, Neo Geo Pocket]
-
A.
mobileVariant
chosen
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
B.
supportsHandheldMode
Indicates that an entity is capable of operating or being used in a handheld mode.
-
C.
designedForOneHandUse
Indicates that something is intended or optimized to be used comfortably and effectively with only one hand.
-
D.
hasLowPowerVariant
Indicates that an entity has a related version or configuration designed to operate with reduced power consumption compared to the standard one.
-
E.
targetFormFactor
Indicates the specific physical configuration or design format that something is intended to be used with or fit into.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b09ee1e88190a04d42b8251eaa13 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:54 p.m.