Triple
T30472110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximum Firepower |
E775330
|
entity |
| Predicate | hasPoliticalCharge |
P109963
|
FINISHED |
| Object | politically charged |
—
|
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: politically charged | Statement: [Maximum Firepower, hasPoliticalCharge, politically charged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalCharge Context triple: [Maximum Firepower, hasPoliticalCharge, politically charged]
-
A.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
B.
hasLegalCharge
Indicates that one entity holds formal legal responsibility, authority, or custody over another entity or asset.
-
C.
accusedPoliticalAlignment
Indicates that one entity has been accused of holding, supporting, or being associated with a particular political alignment or ideology by another party or source.
-
D.
hasPoliticalComponent
chosen
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
E.
hasPoliticalActivityIn
Indicates that an entity engages in or is associated with political activities within a specified location or jurisdiction.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 8:11 p.m.