Triple
T32066761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kairi |
E818900
|
entity |
| Predicate | seriesDeveloper |
P107754
|
FINISHED |
| Object | Square Enix |
—
|
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: Square Enix | Statement: [Kairi, seriesDeveloper, Square Enix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesDeveloper Context triple: [Kairi, seriesDeveloper, Square Enix]
-
A.
gameDeveloperOfSeries
Indicates that a person or company is the developer responsible for creating or producing one or more games within a particular game series.
-
B.
developerOfSeries
chosen
Indicates that an entity is the creator or primary developer responsible for producing a particular series.
-
C.
coSeriesDeveloper
Indicates that two or more entities jointly developed or created a series together.
-
D.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
E.
gameDeveloperOfWorkAppearsIn
Indicates that a person or entity is the developer of a game in which the referenced work (e.g., character, story, or asset) appears.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 12:22 a.m.