Triple
T33422674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlefield series |
E855884
|
entity |
| Predicate | hasInfantryClass |
P164186
|
FINISHED |
| Object | Assault |
—
|
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: Assault | Statement: [Battlefield series, hasInfantryClass, Assault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfantryClass Context triple: [Battlefield series, hasInfantryClass, Assault]
-
A.
hasInfantryCapability
Indicates that an entity possesses the ability or resources to conduct operations using infantry forces.
-
B.
hasMilitaryClass
chosen
Indicates that an entity belongs to, is assigned to, or is categorized under a specific military class or classification.
-
C.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
D.
hasCivilianClass
Indicates that an entity is associated with or belongs to a particular civilian classification or category.
-
E.
usesInfantryFightingVehicle
Indicates that an entity employs or operates an infantry fighting vehicle as part of its activities or operations.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: May 1, 2026, 1:36 a.m.