Triple
T37456001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyalist Item Pack |
E930800
|
entity |
| Predicate | developerOfRelatedGame |
P35248
|
FINISHED |
| Object | Crate 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: Crate Entertainment | Statement: [Loyalist Item Pack, developerOfRelatedGame, Crate Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerOfRelatedGame Context triple: [Loyalist Item Pack, developerOfRelatedGame, Crate Entertainment]
-
A.
developerOfContainingGame
Indicates that an entity is the developer responsible for creating the game that contains the referenced element or component.
-
B.
gameDeveloper
chosen
Indicates that one entity creates, designs, or develops the other entity, which is a game.
-
C.
gameDeveloperOfOrigin
Indicates that an entity is the original creator or primary developing studio responsible for a particular game.
-
D.
developerOfGameUsed
Indicates that an entity is the developer of a game that is (or was) used or played in a given context.
-
E.
gameDeveloperOwner
Indicates that one entity is the owner or primary controlling developer of a particular game.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 3, 2026, 4:17 p.m.