Triple
T38634558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal (Call of Duty: Modern Warfare 2 map) |
E937542
|
entity |
| Predicate | hasLongSightlines |
P191305
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Terminal (Call of Duty: Modern Warfare 2 map), hasLongSightlines, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongSightlines Context triple: [Terminal (Call of Duty: Modern Warfare 2 map), hasLongSightlines, true]
-
A.
hasSight
Indicates that one entity possesses the ability or capacity to see or visually perceive.
-
B.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
C.
hasSniperLinesOfSight
chosen
Indicates that one entity has a clear, unobstructed line of sight suitable for sniper fire to another entity or location.
-
D.
lineOfSight
Indicates that one entity has an unobstructed visual path to another entity.
-
E.
hasInclinationToLineOfSight
Indicates that one entity is oriented or directed in such a way that it tends toward having a line of sight to another entity or location.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
Created at: May 3, 2026, 4:32 p.m.