Triple
T25201831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobius Digital |
E631142
|
entity |
| Predicate | publisherForOuterWilds |
P164166
|
FINISHED |
| Object | Annapurna Interactive |
—
|
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: Annapurna Interactive | Statement: [Mobius Digital, publisherForOuterWilds, Annapurna Interactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherForOuterWilds Context triple: [Mobius Digital, publisherForOuterWilds, Annapurna Interactive]
-
A.
publisherInUniverse
Indicates that a publisher operates, exists, or is recognized within a particular fictional or conceptual universe.
-
B.
coPublisher
Indicates that two or more entities jointly publish the same work or content.
-
C.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
D.
publisherOfStories
Indicates that one entity serves as the publisher responsible for releasing or distributing the stories created by another entity.
-
E.
correctedEditionPublisher
Indicates that a publisher is responsible for issuing a corrected edition of a previously published work.
- F. None of above. chosen
Provenance (4 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 21, 2026, 12:51 p.m.