Triple
T30480983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amiga CD32 |
E775584
|
entity |
| Predicate | plannedReleaseRegion |
P35878
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Amiga CD32, plannedReleaseRegion, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedReleaseRegion Context triple: [Amiga CD32, plannedReleaseRegion, United States]
-
A.
releasePlatformRegion
Indicates the specific geographic region or market where a release (such as a product, service, or media title) is made available on a given platform.
-
B.
releaseRegion
chosen
Indicates the geographic or jurisdictional area in which something (such as a product, service, or content) is made available or officially released.
-
C.
reReleasedInCountry
Indicates that a previously released work was released again in a specified country.
-
D.
developedInRegion
Indicates that something was created, produced, or brought into existence within a specified geographic region.
-
E.
regionTypePlanned
Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:12 p.m.