Triple
T29371765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson Soft HuC6270 |
E744872
|
entity |
| Predicate | regionVariantsUsedIn |
P39014
|
FINISHED |
| Object | PC Engine CoreGrafx |
—
|
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: PC Engine CoreGrafx | Statement: [Hudson Soft HuC6270, regionVariantsUsedIn, PC Engine CoreGrafx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionVariantsUsedIn Context triple: [Hudson Soft HuC6270, regionVariantsUsedIn, PC Engine CoreGrafx]
-
A.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
B.
hasRegionalVariationsIn
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
C.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
D.
regionCodeUsedIn
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
E.
usedInVariant
chosen
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 2:27 p.m.