Triple
T36240735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncharted: The Nathan Drake Collection |
E891510
|
entity |
| Predicate | basedOnGameByStudio |
P97759
|
FINISHED |
| Object | Naughty Dog |
—
|
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: Naughty Dog | Statement: [Uncharted: The Nathan Drake Collection, basedOnGameByStudio, Naughty Dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnGameByStudio Context triple: [Uncharted: The Nathan Drake Collection, basedOnGameByStudio, Naughty Dog]
-
A.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
-
B.
gamePublisherOfAppearance
Indicates that one entity is the publisher responsible for releasing a particular appearance or edition of a game.
-
C.
developedGameBasedOn
chosen
Indicates that one game was created or designed using another game as its source of inspiration, foundation, or reference.
-
D.
gamePublisherOfWork
Indicates that one entity is the publisher responsible for releasing or distributing a particular game work.
-
E.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.