Triple
T22906281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Norfolk (1991) |
E568451
|
entity |
| Predicate | opposingWeaponSystem |
P150181
|
FINISHED |
| Object | T-72 main battle tank |
—
|
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: T-72 main battle tank | Statement: [Battle of Norfolk (1991), opposingWeaponSystem, T-72 main battle tank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingWeaponSystem Context triple: [Battle of Norfolk (1991), opposingWeaponSystem, T-72 main battle tank]
-
A.
usedOnWeaponSystem
Indicates that something (such as a component, technology, or material) is employed as part of, or in conjunction with, a weapon system.
-
B.
weaponSystemType
Indicates the specific category or kind of weapon system associated with an entity.
-
C.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
D.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
E.
appliesToWeaponSystem
Indicates that something (such as a rule, configuration, or characteristic) is relevant or applicable to a particular weapon system.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801a48948190b5f51f1d02351fc7 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:41 p.m.