Triple
T37928955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xehanort |
E946162
|
entity |
| Predicate | firstFullAppearanceAsXehanort |
P204480
|
FINISHED |
| Object | Kingdom Hearts Birth by Sleep |
E952773
|
NE FINISHED |
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 Birth by Sleep | Statement: [Xehanort, firstFullAppearanceAsXehanort, Kingdom Hearts Birth by Sleep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFullAppearanceAsXehanort Context triple: [Xehanort, firstFullAppearanceAsXehanort, Kingdom Hearts Birth by Sleep]
-
A.
firstAppearanceInLegendarium
Indicates the work or source within a fictional legendarium in which an entity is introduced or mentioned for the first time.
-
B.
firstStageAppearance
Indicates the event or context in which an entity makes its initial appearance on stage.
-
C.
settingOfFirstAppearance
Indicates the location or context in which an entity is first introduced or appears.
-
D.
firstPlayableAppearance
Indicates the earliest work or context in which an entity can be directly controlled or played as a character.
-
E.
firstAppearanceChapter
Indicates the chapter in which an entity (such as a character, item, or concept) is first introduced or appears in a work.
- F. None of above. chosen
Provenance (5 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4223a320908190a760a28d178d817e |
completed | June 29, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.