Triple
T35421696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanilla Ghost House |
E1023811
|
entity |
| Predicate | regionFirstReleased |
P40433
|
FINISHED |
| Object | Japan |
—
|
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: Japan | Statement: [Vanilla Ghost House, regionFirstReleased, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionFirstReleased Context triple: [Vanilla Ghost House, regionFirstReleased, Japan]
-
A.
firstReleaseRegion
chosen
Indicates the geographic region or market where something (such as a product, work, or release) was first made publicly available.
-
B.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
C.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
D.
firstReleasedVia
Indicates the original platform, channel, or medium through which something (such as a product, work, or content) was first released or made available.
-
E.
ukReleaseDate
Indicates the date on which something is released or made publicly available in the United Kingdom.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.