Triple
T11540896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Ward |
E273669
|
entity |
| Predicate | settingSpecialty |
P466
|
FINISHED |
| Object | modern military warfare |
—
|
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: modern military warfare | Statement: [Infinity Ward, settingSpecialty, modern military warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingSpecialty Context triple: [Infinity Ward, settingSpecialty, modern military warfare]
-
A.
hasSpecialty
chosen
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
positionSpecialization
Indicates that one position is a more specialized or focused variant of another, broader position.
-
C.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
D.
escapeSpecialty
Indicates that one entity leaves, avoids, or breaks free from a particular specialized role, field, or area of expertise associated with another entity.
-
E.
creatorSpecialization
Indicates the specific field, discipline, or area of expertise in which a creator primarily works or is specialized.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.