Triple
T36958550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railgun (Quake) |
E914248
|
entity |
| Predicate | primaryWeakness |
P47330
|
FINISHED |
| Object | slow rate of fire |
—
|
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: slow rate of fire | Statement: [Railgun (Quake), primaryWeakness, slow rate of fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWeakness Context triple: [Railgun (Quake), primaryWeakness, slow rate of fire]
-
A.
initialWeakness
Indicates that an entity has a vulnerability or disadvantage present at the beginning of a process, event, or interaction.
-
B.
hasWeakness
chosen
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
C.
primarySymptom
Indicates that the related symptom is the main or most characteristic symptom associated with a condition, disease, or disorder.
-
D.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
-
E.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.