Triple
T37929114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom Hearts II |
E946164
|
entity |
| Predicate | expandedVersion |
P103636
|
FINISHED |
| Object | Kingdom Hearts II Final Mix |
—
|
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: Kingdom Hearts II Final Mix | Statement: [Kingdom Hearts II, expandedVersion, Kingdom Hearts II Final Mix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedVersion Context triple: [Kingdom Hearts II, expandedVersion, Kingdom Hearts II Final Mix]
-
A.
expandedVersionForm
Indicates that one entity is an expanded or more fully written-out version of another entity’s form.
-
B.
expandedVersionTitle
chosen
Indicates that one title is the name used for an expanded or extended version of another work.
-
C.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
D.
expandedForm
Indicates that one representation is the expanded or fully written-out form of another, typically decomposing it into a sum or more detailed expression.
-
E.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:20 p.m.