Triple
T36953362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammer of Dawn |
E914129
|
entity |
| Predicate | developedByFranchise |
P139083
|
FINISHED |
| Object | Epic 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: Epic Games | Statement: [Hammer of Dawn, developedByFranchise, Epic Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedByFranchise Context triple: [Hammer of Dawn, developedByFranchise, Epic Games]
-
A.
developerOfFranchise
chosen
Indicates that an entity is the creator or primary developer responsible for originating or establishing a particular franchise.
-
B.
formedByFranchise
Indicates that something (such as a team, organization, or unit) was created or established as a result of a franchise agreement or franchising process.
-
C.
gameFranchise
Indicates that one entity is a video game franchise to which the other entity (such as a specific game, character, or related media) belongs or is associated.
-
D.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
-
E.
developedByCharacter
Indicates that something (such as an item, technique, or work) was created, designed, or brought into existence by a particular character.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:13 p.m.