Triple
T35010988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunset Sarsaparilla |
E1009937
|
entity |
| Predicate | developerCreator |
P35248
|
FINISHED |
| Object | Obsidian Entertainment |
—
|
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: Obsidian Entertainment | Statement: [Sunset Sarsaparilla, developerCreator, Obsidian Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerCreator Context triple: [Sunset Sarsaparilla, developerCreator, Obsidian Entertainment]
-
A.
gameDeveloper
chosen
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
B.
developerOfSeries
Indicates that an entity is the creator or primary developer responsible for producing a particular series.
-
C.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
D.
créateur
Indicates that an entity is the creator or originator of another entity.
-
E.
creatorType
Indicates the role or category of a creator in relation to the creation of something (e.g., author, artist, director).
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:01 p.m.