Triple
T38464628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fake Crash |
E912531
|
entity |
| Predicate | hasOriginalDeveloperContext |
P180630
|
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: [Fake Crash, hasOriginalDeveloperContext, Naughty Dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalDeveloperContext Context triple: [Fake Crash, hasOriginalDeveloperContext, Naughty Dog]
-
A.
hasOriginalProducer
Indicates that an entity was initially created, manufactured, or produced by a specific producer or organization.
-
B.
hasOriginalClient
Indicates that an entity is associated with the initial or primary client for whom it was originally created, configured, or served.
-
C.
hasDeveloperType
Indicates that an entity is associated with a specific category or type of developer.
-
D.
hasOriginalRole
Indicates that an entity previously held a particular role or function before a change to its current role.
-
E.
developedByContext
chosen
Indicates that something was developed or created within, and influenced by, a particular contextual setting or circumstances.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 3, 2026, 4:31 p.m.