Triple
T37466437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortex Vortex |
E931044
|
entity |
| Predicate | originalDeveloperOfFranchise |
P39805
|
FINISHED |
| Object | Naughty Dog |
E240599
|
NE FINISHED |
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: Naughty Dog | Statement: [Cortex Vortex, originalDeveloperOfFranchise, Naughty Dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDeveloperOfFranchise Context triple: [Cortex Vortex, originalDeveloperOfFranchise, Naughty Dog]
-
A.
developerOfFranchise
Indicates that an entity is the creator or primary developer responsible for originating or establishing a particular franchise.
-
B.
gameDeveloperOfOrigin
Indicates that an entity is the original creator or primary developing studio responsible for a particular game.
-
C.
originalDevelopers
Indicates that the specified entities are the ones who initially created or developed the referenced item, project, or work.
-
D.
gameDeveloperOfSeries
Indicates that a person or company is the developer responsible for creating or producing one or more games within a particular game series.
-
E.
franchiseCreatorOf
chosen
Indicates that an entity is the original creator or originator of a particular franchise.
- F. None of above.
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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408c350b108190ac0a7f933544bd3a |
completed | June 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.