Triple
T28898489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evil the Cat |
E732891
|
entity |
| Predicate | franchiseDeveloper |
P139083
|
FINISHED |
| Object | Shiny 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: Shiny Entertainment | Statement: [Evil the Cat, franchiseDeveloper, Shiny Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseDeveloper Context triple: [Evil the Cat, franchiseDeveloper, Shiny Entertainment]
-
A.
developerOfFranchise
chosen
Indicates that an entity is the creator or primary developer responsible for originating or establishing a particular franchise.
-
B.
franchiseCreatorOf
Indicates that an entity is the original creator or originator of a particular franchise.
-
C.
publisherOfFranchise
Indicates that an entity serves as the publishing company responsible for releasing or distributing a particular franchise.
-
D.
majorDeveloper
Indicates that an entity is a primary or leading developer responsible for creating or significantly contributing to another entity.
-
E.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8:01 a.m.