Triple
T38477246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wumpa Fruit |
E915579
|
entity |
| Predicate | developerAssociatedWith |
P23571
|
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: [Wumpa Fruit, developerAssociatedWith, Naughty Dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerAssociatedWith Context triple: [Wumpa Fruit, developerAssociatedWith, Naughty Dog]
-
A.
developerOfWork
chosen
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
B.
coDeveloperOf
Indicates that two or more entities jointly developed or collaborated in creating the same project, product, or work.
-
C.
leadDeveloperAlias
Indicates that one entity serves as an alternative or alias name for the lead developer associated with another entity.
-
D.
hasDeveloperRelation
Indicates a relationship in which one entity serves as the developer, creator, or builder of another entity.
-
E.
developmentLedBy
Indicates that the development of something is directed, managed, or overseen by a particular agent or 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 3, 2026, 4:31 p.m.