Triple
T37468083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bianca |
E931080
|
entity |
| Predicate | gameDeveloperOfOrigin |
P187970
|
FINISHED |
| Object | Insomniac Games |
—
|
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: Insomniac Games | Statement: [Bianca, gameDeveloperOfOrigin, Insomniac Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameDeveloperOfOrigin Context triple: [Bianca, gameDeveloperOfOrigin, Insomniac Games]
-
A.
gameDeveloper
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
B.
gameDeveloperOfAppearance
Indicates that an entity is the developer responsible for creating or producing a particular appearance or version of a game.
-
C.
gameDeveloperOfSeries
Indicates that a person or company is the developer responsible for creating or producing one or more games within a particular game series.
-
D.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
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. 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.