Triple
T12160697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-80 |
E289696
|
entity |
| Predicate | canFireATGMThroughGun |
P103273
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [T-80, canFireATGMThroughGun, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canFireATGMThroughGun Context triple: [T-80, canFireATGMThroughGun, yes]
-
A.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
-
B.
hasSmokeGrenadeLaunchers
Indicates that an entity is equipped with or possesses smoke grenade launching devices.
-
C.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
D.
grenadeLauncherCompatibility
Indicates that one entity can be equipped with, mounted to, or used in conjunction with a particular grenade launcher.
-
E.
rocketArmament
Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d915d58ab881908b5b7901990308a4 |
completed | April 10, 2026, 3:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.