Triple
T37803983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivet |
E942453
|
entity |
| Predicate | homeFranchiseDeveloper |
P139083
|
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: [Rivet, homeFranchiseDeveloper, Insomniac Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFranchiseDeveloper Context triple: [Rivet, homeFranchiseDeveloper, Insomniac Games]
-
A.
homeFranchisePlatform
Indicates that a franchise operates primarily through a home-based business model supported by a specific platform or system.
-
B.
franchiseStarterFor
Indicates that one entity is the initial or primary franchise location, product, or person from which a broader franchise operation is launched or developed for another entity.
-
C.
developerOfFranchise
chosen
Indicates that an entity is the creator or primary developer responsible for originating or establishing a particular franchise.
-
D.
studioFranchise
Indicates that a studio is associated with, produces, or manages a particular franchise.
-
E.
launchesFranchise
Indicates that one entity initiates and establishes a new franchise operation or brand based on another entity.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.