Triple
T38634572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal (Call of Duty: Modern Warfare 2 map) |
E937542
|
entity |
| Predicate | hasSpawnPoints |
P18866
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Terminal (Call of Duty: Modern Warfare 2 map), hasSpawnPoints, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpawnPoints Context triple: [Terminal (Call of Duty: Modern Warfare 2 map), hasSpawnPoints, multiple]
-
A.
spawningLocation
chosen
Indicates the place or environment where an entity originates, appears, or is generated.
-
B.
hasAttackingTeamSpawn
Indicates that a location or point is designated as the spawn area for the attacking team.
-
C.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
-
D.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
E.
hasWeaponSpawn
Indicates that a location, object, or entity serves as a spawn point where weapons can appear or be generated.
- 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_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:32 p.m.