Triple
T37685813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascendance |
E938362
|
entity |
| Predicate | developedForGame |
P196109
|
FINISHED |
| Object | Call of Duty: Advanced Warfare |
—
|
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: Call of Duty: Advanced Warfare | Statement: [Ascendance, developedForGame, Call of Duty: Advanced Warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForGame Context triple: [Ascendance, developedForGame, Call of Duty: Advanced Warfare]
-
A.
developedForProgram
Indicates that something was created, designed, or produced specifically to be used in or support a particular program.
-
B.
developedForProduct
Indicates that something (such as a component, feature, or service) was specifically created or tailored to be used with or support a particular product.
-
C.
developedGameBasedOn
Indicates that one game was created or designed using another game as its source of inspiration, foundation, or reference.
-
D.
developedSystemFor
Indicates that one entity created or engineered a system intended to be used by or on behalf of another entity.
-
E.
developerOfGameUsed
Indicates that an entity is the developer of a game that is (or was) used or played in a given context.
- F. None of above. chosen
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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.