Triple
T38634574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal (Call of Duty: Modern Warfare 2 map) |
E937542
|
entity |
| Predicate | hasDestructibleElements |
P201319
|
FINISHED |
| Object | limited |
—
|
LITERAL 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: limited | Statement: [Terminal (Call of Duty: Modern Warfare 2 map), hasDestructibleElements, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDestructibleElements Context triple: [Terminal (Call of Duty: Modern Warfare 2 map), hasDestructibleElements, limited]
-
A.
isRepairable
Indicates that an entity can be restored to proper working condition through repair.
-
B.
hasDemolitionOrDestruction
Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of another entity.
-
C.
designedToBeDismantled
Indicates that something was intentionally created or constructed so that it can later be taken apart or disassembled.
-
D.
canBeBrokenByHand
Indicates that the object is fragile or weak enough to be physically broken using only human hands, without tools or machinery.
-
E.
hasDestructibleCities
Indicates that the subject possesses or includes cities that are capable of being destroyed.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
| PDg | Predicate description generation | batch_69ffe8eb47d48190acf7794ebe3ef4b8 |
completed | May 10, 2026, 2:09 a.m. |
Created at: May 3, 2026, 4:32 p.m.